Administration · LessonBy Praveen T, ServiceNow Trainer, 9 yrs · Published · Updated · current release · beginner
Administration basics
What a ServiceNow admin actually does day to day.
Quick answer
Administration is the everyday craft of keeping an instance healthy, secure and configured to the business. It is also the ground the CSA exam covers most heavily.
Key takeaways
- What an administrator owns
- Everyday tools
- Impersonation done right
- Keeping the instance running
- The golden rule of change
Administration is the everyday craft of keeping an instance healthy, secure and configured to the business. It is also the ground the CSA exam covers most heavily. A good admin thinks in terms of five responsibilities, access, configuration, data, change control and health, and knows the tools for each without reaching for code first.
What an administrator owns
Everyday tools
- Application Navigator / All menu, filter to any module instantly (try
sys_properties.list). - Impersonate, view the instance exactly as another user, without their password. The single most useful admin habit.
- System Properties (
sys_properties), instance-wide switches. Powerful and global; change with care. - Plugins & the Store, activate platform features and install apps.
- System Definition, the tables behind dictionaries, business rules, UI actions, and more.
Impersonation done right
Before you ship any access change, impersonate an
itil user and an end user and confirm they see exactly what they should, no more, no less. Impersonation also runs notifications and ACLs as that user, so it is the fastest way to reproduce a "why can't they see this?" ticket.Keeping the instance running
- System Logs (
syslog), Node Log File Download, and the Transaction (all user) logs are your first stops when something misbehaves. - Scheduled Jobs run recurring work, watch for ones that overrun or error; see Scheduled jobs.
- Stats.do / Slow queries help diagnose performance.
- Upgrades arrive with each family release, review skipped and changed records afterward via the upgrade history.
The golden rule of change
Never build in production. Configure in a sub-prod instance, capture it in an update set, and promote it. Editing prod directly is how instances rot, collide on the next upgrade, and become impossible to move between environments.
Common mistakes
- Granting
adminto solve an access problem a role or ACL should handle. - Editing production directly instead of promoting an update set.
- Changing a global system property without understanding its blast radius.
- Ignoring the upgrade skipped/changed report and losing customisations silently.
Practice challenge
+0 XPStreak ×0
Question 1 of 3
Most ServiceNow administration is done through...
Frequently asked questions
What does the term Administration basics refer to in ServiceNow?
Administration is the everyday craft of keeping an instance healthy, secure and configured to the business. It is also the ground the CSA exam covers most heavily.
What is the performance impact of Administration basics?
System Logs (syslog), Node Log File Download, and the Transaction (all user) logs are your first stops when something misbehaves. Stats.do / Slow queries help diagnose performance. Upgrades arrive with each family release, review skipped and changed records afterward via the upgrade history.
What is the practical takeaway on Administration basics?
Application Navigator / All menu, filter to any module instantly (try sys_properties.list). Impersonate, view the instance exactly as another user, without their password. The single most useful admin habit.
What tends to go wrong with Administration basics?
Granting admin to solve an access problem a role or ACL should handle. Editing production directly instead of promoting an update set. Changing a global system property without understanding its blast radius.