The burden of being a system administrator
I became a system admin early in my career during a large system install. It was great! I got all kinds of new permissions, could do (almost) anything and it felt great.
What I didn't realize is that being a sys admin is more than getting extra permissions or access to new areas. Sure that's part of it's but being made a sys admin for any system is massive responsibility, and one that needs to be taken seriously.
This is doubly true if the system you administer handles any kind of sensitive data.. things like personally identifiable info, compensation data and the like. This information needs.to be carefully guarded and managed as it cause cause massive headaches if it gets out.
Even if you aren't the sys admin for a sensitive system, however, you still take on a lot of responsibilities.
Appropriate access
You will likely need to manage access to your system. This could involve adding new users changing existing access or revoking it as needed. You shouldn't also be the person who can approve access, so you'll need to follow a process and work with your approvers.
You should be very proactive with this part of being an admin. After all, you're being trusted to ensure only folks who should have access have it. This means you should be doing things like :
Regular audits - review who has what type of access andnget.it reapproved on a regular basis (quarertly, half-year).
Taking prompt action - This is especially true when a request to revoke access comes in. Make sure the person requesting it is authorized (e.g. a system owner, HR rep, legal etc), and then don't wait. 'This, however, also applies to other requests. Quick action both helps ensure the system is managed properly and helps build your credibility.
Be proactive - Be on the lookout for things that seem out of place, updates that are needed,
Troubleshooting
Since you have a ton of additional system access (frequently including the ability to see access log, or even log in as someone else) you will find yourself frequently having to troubleshoot issues. You also likely have a much deeper set of exoerienxes with ehateber system you're the admin for - both as a result of being and admin, but also because you interact with a wide range of system users.
This puts you in a strong position to help others learn to use the system or overcome challenges they find in it. These could be small questions, to massive disruptions. Regardless of the size, however, it is your job is to help solve it.
This could mean building documentation that folks can refer to, running training sessions, recording demonstrations and more. While each of these on their own may be a small thing, they add up over time, and help others more effective use the system.
Best practices
Typically being a sys admin goes beyond just pushing buttons to do things and moves into providing guidance and ideas on best practice. What is the best way to use the tool? What should it not be used for? What should we do now so we can do X in the future?
This area goes beyond technical knowledge of the system and gets into how the tool can be used. As an admin you likely are exposed to more ways a system can be utilized - this gives you a good perspective on how your team should use it.
Advising on best practices shows up in two main places - during planning and on an ongoing basis. Both involve you offering your expertise and knowledge, and both will require you to partner with whomever is looking to modify or use the system.
Wrap up
Being a sys admin can be a very fulfilling job. You'll learn a ton about the tech, and about the busiess. And even better, you'll help others do better at their jobs by removing friction and helping knock down blockers.
