ServiceNow fundamentals
The handful of concepts every ServiceNow role rests on.
Before any single product makes sense, a handful of platform fundamentals do most of the explaining. Master these and every module you meet later, incident, CMDB, catalog, HR case, is just the same machinery pointed at a different table.
- Applications, modules and navigation
- Lists and forms, the two views you live in
- Access: roles, groups and ACLs
- Automation: how records react
- Moving change safely
Before any single product makes sense, a handful of platform fundamentals do most of the explaining. Master these and every module you meet later, incident, CMDB, catalog, HR case, is just the same machinery pointed at a different table. This lesson walks the core building blocks in the order they build on each other.
Lists and forms, the two views you live in
Almost all work is one loop: filter a list, open a record on a form, change fields, save. Everything underneath is a record on a table.
Access: roles, groups and ACLs
What a user can see and do is decided in three layers, each covered in depth elsewhere:
admin is the superuser; itil the everyday fulfiller; ess the self-service user. Detail lives in Users, groups & roles and ACLs & security.
Automation: how records react
Records do not just sit there, the platform responds to changes at several layers. Knowing where each runs is fundamental:
Rule of thumb: reach for the least powerful tool that does the job, a data policy before a business rule, a flow before hand-written code.
Moving change safely
Configuration is built in a sub-production instance and captured into update sets (or a scoped-app version), then promoted dev, test, prod. This discipline, never hand-editing production, is what keeps a platform stable. See Update sets.
Where end users actually land
Requesters rarely see these back-end forms. They use the Service Portal / Employee Center / mobile app, a friendly front door onto the same catalog, knowledge and requests. Agents increasingly work in configurable Workspaces rather than the classic form.
Common mistakes
- Using Configure when you meant Personalize, changing everyone's layout.
- Reaching straight for scripting when a UI policy, data policy or flow would do it no-code.
- Editing production directly instead of promoting an update set.
- Not learning the data model first, so every module feels brand new.