Domain 1: Platform Overview and Navigation
- Next Experience is the current ServiceNow user interface; its unified navigation bar provides the All, Favorites, History, and Workspaces menus alongside global search, notifications, and the user avatar menu.
- The All menu holds the Application Navigator, which lets users search and browse to any application or module they have role-based access to.
- Typing in the All menu's filter box instantly narrows the list of modules to matching names, which is faster than manually expanding menus.
- Clicking the star icon next to a module, record, or report adds it to that user's personal Favorites, and Favorites can be organized into groups.
- The History menu automatically tracks recently viewed modules and records without any manual action, unlike Favorites which must be deliberately starred.
- List views display table records in rows and columns; right-clicking a column header opens the list context menu for actions like sorting, grouping, and exporting.
- Personalize Columns lets a user choose which fields appear in a list and in what order, without changing the underlying table.
- Double-clicking a cell in a list enables inline (list) editing so a value can be updated without opening the full form.
- The condition builder lets a user visually construct filter conditions (field, operator, value) to narrow a list without writing a query string.
- Breadcrumbs above a filtered list display the active filter, sort, and group conditions in plain, readable text.
- Impersonate lets an administrator temporarily experience the instance as another user, seeing exactly what that user's roles allow, for testing and troubleshooting.
Domain 2: Instance Configuration
- Plugins add or extend platform features, and an administrator finds and activates them under All > System Applications > All Available Applications; older releases used System Definition > Plugins.
- Before requesting or activating a plugin, an administrator should check whether it is already active on the instance, because some plugins are activated by default or by other plugins.
- Some plugins need a separate subscription and must be activated by ServiceNow personnel, while a Personal Developer Instance can activate most plugins without requesting or purchasing them.
- System properties are stored in the System Properties [sys_properties] table, and typing sys_properties.list in the navigator opens the full list so an administrator can view or change a property value.
- In Core UI, the Basic Configuration UI16 page under System Properties sets the banner logo, page title, and interface colors for the instance.
- In Next Experience, branding is applied through themes; Theme Builder walks an administrator through a primary brand color, a neutral color, a logo, a font, and corner shape.
- ServiceNow stores all date and time values in Coordinated Universal Time (UTC) and displays them in the time zone of the system or of the individual user.
- The glide.sys.default.tz property sets the system default time zone, and a user's own time zone setting in their profile overrides that default for that user.
- Location-based time zones such as America/Los_Angeles adjust for daylight saving time automatically, while zones named generically, such as GMT, typically do not.
- American English is the platform's default language, and a user with the admin role can activate I18N translation plugins to add other supported languages that users then choose in their preferences.
- Localization plugins cannot be uninstalled after installation, so a language should be activated and tested on a sub-production instance before production.
Domain 3: Configuring Applications for Collaboration
- The Activity formatter on a form renders a single chronological feed combining work notes, additional comments, and tracked field changes, newest entries first by default.
- Work notes are a journal-type field visible only to users with fulfiller-level roles, used for internal collaboration on a task.
- Additional comments are a journal-type field visible to the requester or caller as well as fulfillers, used for customer-facing updates.
- Both work notes and additional comments are append-only journal fields, so every entry is timestamped and preserved rather than overwritten.
- Typing @ in a journal field opens a type-ahead list to mention a specific user or group; the mentioned user is notified only if mention notifications are enabled.
- A caller's email reply to a notification is typically appended to the additional comments field on the associated record.
- Connect Chat and Live Feed provide real-time, in-platform conversation tied to a specific record or topic, separate from the asynchronous journal fields.
- Notifications are generated from notification records that fire on table events such as insert or update, or on scheduled conditions, and are delivered by email or in-platform alerts.
- Visual Task Boards give teams a Kanban-style, drag-and-drop view of tasks for lightweight team collaboration outside the core ticket forms.
- Agent Workspace centralizes a fulfiller's assigned records, activity feed, and collaboration tools in one UI optimized for high-volume ticket handling.
- Knowledge Management organizes articles into knowledge bases and categories, and supports a workflow of draft, review, publish, and retire, along with versioning and user feedback.
- UI policies control field behavior, such as visible, mandatory, or read-only, on the client dynamically as a form is used, while data policies enforce the same kind of rules server-side regardless of which client submits the data.
- Client scripts run in the browser, triggered by onLoad, onChange, onSubmit, or onCellEdit, to control form behavior in response to user actions without a server round trip.
- A List report simply renders matching records in rows and columns, the same as a filtered list view, without aggregating them into groups.
- A pie or donut chart shows each category's share of a whole and reads clearly only with a small number of categories; too many slices become hard to compare.
- Bar and column charts plot one bar per category and scale better than pie or donut charts when there are many categories to compare.
- A pivot table cross-tabulates two dimensions, one as rows and one as columns, with aggregated values filling each cell; a pivot chart visualizes the same cross-tab.
- A trend or time series report plots a metric against a date/time axis, grouping records by an interval such as day, week, or month.
- A single score report displays one aggregated headline number with no dimensional breakdown.
- A calendar report plots records with start and/or end dates onto a calendar grid, so it requires a usable date field.
- Performance Analytics differs from standard reporting by capturing periodic snapshots, or scores against indicators, over time, enabling trend analysis, whereas reporting queries live, real-time data.
- Reports can be shared with specific users, roles, or groups, and scheduled to run and be emailed on a recurring basis.
- Dashboards assemble multiple reports and widgets onto one responsive page, and can be shared the same way as individual reports.
- Group by and stack by settings on a chart control the primary category axis and an additional breakdown within each bar or segment.
Domain 4: Self Service and Automation
- A catalog item, stored in the sc_cat_item table, is an orderable product or service, such as hardware or software, that a user requests through the Service Catalog.
- Catalog categories group related catalog items for browsing, and categories can be nested into subcategories for larger catalogs.
- Deactivating a catalog item by setting Active to false removes it from ordering and browsing while preserving the record and its configuration for later reuse.
- Ordering a catalog item generates a Requested Item (RITM) under a Request, along with catalog tasks that fulfillers work to completion; a knowledge article, by contrast, is documentation with no fulfillment process.
- A record producer lets an end user submit a form that creates a record directly on a target table, such as Incident, rather than generating a requested item.
- An order guide bundles several related catalog items into one guided request, such as a new-hire onboarding kit, and can even nest other order guides.
- Catalog variables, including single line text, select box, reference, and checkbox types, collect the specific input needed from the person placing an order.
- Variable sets bundle a reusable group of variables that can be applied across multiple catalog items instead of recreating the same variables each time.
- Flow Designer builds flows and reusable subflows from triggers and no-code actions, and is the modern replacement for the legacy Workflow editor for automating processes; current releases open it from Workflow Studio.
- Approvals route a record to one or more approvers who can approve or reject it, driving downstream workflow logic such as releasing a change or fulfilling a catalog request.
- Service Level Agreements (SLAs) attach to tasks to track and enforce time commitments, and support pause conditions and retroactive application to catch already-open records.
- Business rules run server-side scripts before, after, asynchronously after, or on display of a record, based on insert, update, delete, or query events.
Domain 5: Database Management and Platform Security
- Every piece of data in the platform is stored in a table, and every table's structure is defined by dictionary entries (sys_dictionary) describing its fields.
- Table Administration, under System Definition > Tables, lets an administrator view and configure any table, including its parent table, columns, and related dictionary records.
- A table has both a Name, the fixed technical identifier used by scripts and the database, and a Label, the friendly display name; renaming the Label never changes the Name.
- Tables can extend a parent table to inherit all of its fields and behavior; for example, Incident, Problem, and Change Request all extend the base Task [task] table.
- Extending a table centralizes shared fields and logic on the parent, so a new child table automatically reuses everything already defined on that parent.
- Custom fields added while working in the Global scope are automatically prefixed with u_, while fields added inside a scoped application are prefixed with the app's own scope identifier.
- The sys_ prefix is reserved for baseline, out-of-box platform tables and fields and should not be reused for custom fields.
- Reference fields point to a record on another table, and dot-walking lets a form, list, report, or script traverse that reference to pull a field from the related record.
- Field types include string, integer, choice, reference, date/time, true/false (boolean), and journal (append-only), each governing how the platform stores and renders that column's data.
- A Number Maintenance record defines the auto-numbering prefix and next-number counter used when new records are created on a given table.
- Database views join fields from two or more related tables into a single reportable, read-only virtual table without duplicating the underlying data.
- The User [sys_user] table stores each person's core identity data, such as name, email, and login credentials; sys_user_group stores groups, sys_user_has_role stores role assignments, and sys_user_grmember stores group membership.
- Unchecking Active on a user record disables login for that account while preserving the record and its references on existing tasks and incidents; deleting the record would break those references.
- Locked out marks an account as blocked from logging in, which the platform can set automatically after repeated failed login attempts or which an administrator can set manually.
- Roles grant access to applications, modules, and data, can themselves contain other roles, and are assigned to users directly or inherited through group membership.
- A role assigned on a group's Roles tab is inherited by every member of that group.
- Access Control Lists (ACLs) secure records and fields per operation, such as read, write, create, or delete, against a table and field, and are evaluated using roles, a condition, and a script together.
- ACLs are default-deny: access is granted only when a matching ACL's requirements are all satisfied, and without a matching, satisfied ACL, access is denied.
- The wildcard field name * on an ACL applies that rule to every field on the table unless a more specific, field-level ACL also exists, since the platform evaluates the most specific matching ACL first.
- The Configuration Management Database (CMDB) stores configuration items (CIs) and the relationships between them, and CI classes such as servers and applications extend the base Configuration Item [cmdb_ci] table.
- The Identification and Reconciliation Engine (IRE) applies identification rules to recognize an existing CI and reconciliation rules to decide which data source may update it, which keeps duplicate CIs out of the CMDB.
- The Common Service Data Model (CSDM) is ServiceNow's standard data model for structuring CIs and their relationships in the CMDB, and its Foundation domain holds the base data, such as companies, locations, and groups, that the other domains reference.
- Security Center, opened from All > Security Center, includes security posture dashboards with an instance hardening compliance score that lists recommended security settings by priority and potential impact.
- Under the shared responsibility model, ServiceNow secures the platform and the infrastructure it runs on, while each customer is responsible for securing how its own instance is configured, including authentication, access rights, and the data it stores.
Domain 6: Data Migration and Integration
- Import sets stage raw source data in their own import set table so it can be reviewed and transformed on a controlled schedule instead of writing straight into a target table.
- A JDBC data source connects live to an external relational database using a driver and connection string, without needing a manually exported file.
- A File data source reads an uploaded CSV, Excel, or XML attachment into a staging table, matching a one-time spreadsheet import scenario.
- LDAP data sources query a directory server, such as Active Directory, in real time to bring in users, groups, and related attributes.
- The Import Set REST API lets an external system post records directly into a staging table over REST, without a manually triggered Load Data action.
- A transform map defines how fields on the staging table correspond to fields on the target table, using one or more field maps.
- Coalesce on a transform map field tells the platform to search the target table for an existing record matching that field's value and update it instead of inserting a duplicate; with no match, a new record is inserted.
- Multiple fields coalesced together act as a composite key, so a match requires all of those fields to agree, not just one.
- Transform scripts, such as onBefore, onAfter, and onComplete, run at defined points in the transform to validate, modify, or reject data; onBefore can cancel processing of that row before it is saved.
- Update sets capture configuration changes, such as business rules, ACLs, workflow or flow definitions, and UI policies, made in an instance so they can be moved to another instance; they do not capture data.
- Completing, merging, and backing out update sets are the standard lifecycle actions used to promote or safely reverse a batch of captured customizations between instances.
- A system clone copies a source instance, usually production, over a target sub-production instance; excluded tables arrive with their schema but no data, and data preservers keep chosen target data such as credentials from being overwritten.
- The REST API Explorer lets an administrator build and test REST requests against the instance's own APIs, such as the Table API, before an external system is integrated.
- Integration Hub spokes package ready-made Flow Designer actions for a specific third-party system, so a flow can call that system without custom integration code; many spokes need an Integration Hub subscription.
ServiceNow System Administrator (CSA) exam tips
- Weight your study by the January 2026 blueprint: Database Management and Platform Security is the largest domain at 30 per cent, and Platform Overview and Navigation the smallest at 7 per cent, so tables, ACLs, roles, and the CMDB deserve far more time than menu names.
- Know the work notes vs additional comments distinction cold: work notes are internal/fulfiller-only, additional comments are requester-visible, both are append-only journal fields, and confusing them is one of the most commonly tested collaboration traps.
- Understand table extension and dot-walking together: child tables like Incident, Problem, and Change Request all extend Task and inherit its fields, and dot-walking lets a form, list, or report reach through a reference field into a related record's own fields.
- Memorize ACL evaluation: access requires the user to have one of the ACL's required roles AND the condition to evaluate true AND any script to return true; ACLs are default-deny, and the most specific table.field ACL is evaluated before a wildcard (*) field-level ACL.
- Remember that update sets capture CONFIGURATION, such as business rules, ACLs, UI policies, and flows, for moving between instances, not data; moving records between instances is instead the job of import sets and transform maps, or cloning.
- In transform maps, coalesce marks a field used to look up an existing target record: a match updates that record, no match inserts a new one, and coalescing multiple fields together requires all of them to match as a composite key.
- Do not neglect Instance Configuration: practise activating a plugin, changing a system property, building a theme, and setting system and user time zones on a Personal Developer Instance.
Study guide FAQ
What format and passing requirements does the ServiceNow CSA exam have?
The CSA exam is proctored and has 60 questions to complete in 90 minutes. ServiceNow reports a pass or fail result and does not publish the passing score, so treat any fixed percentage you read elsewhere as unofficial.
Are there any prerequisites for the CSA exam?
ServiceNow does not enforce mandatory prerequisites, but candidates typically complete the System Administration Fundamentals on-demand training, or gain equivalent hands-on experience configuring a ServiceNow instance, before attempting the exam.
What does the CSA exam actually cover?
The January 2026 blueprint has six domains: Platform Overview and Navigation (7 per cent), Instance Configuration (10 per cent), Configuring Applications for Collaboration (20 per cent), Self Service and Automation, Database Management and Platform Security (30 per cent), and Data Migration and Integration. ServiceNow's public page text shows those four weights; secondary study sources put the remaining two at 20 and 13 per cent.
Is hands-on practice important, or can I just study theory?
Hands-on practice matters a great deal. ServiceNow provides a free Personal Developer Instance (PDI); building tables, catalog items, reports, ACLs, and import sets yourself is the best way to internalize how the pieces fit together, and many exam questions describe realistic configuration scenarios rather than pure definitions.
Do I need to know scripting or coding for the CSA exam?
Not extensively. CSA is an administrator-level exam focused on point-and-click configuration; you should recognize basic concepts like business rules, client scripts, and UI versus data policies, but you are not expected to write JavaScript from scratch the way a Certified Application Developer would.
Official exam sources
The domain names and weightings on this page follow the published exam blueprint. Each source below records what it confirmed and when it was read, so the split can be checked rather than taken on trust.
- ServiceNow - Certified System Administrator (CSA) Mainline Exam Blueprint, updated January 2026 (KB0011554)Blueprint revised January 2026 · read 31 October 2026Caveat: The article body loads only after a ServiceNow University sign-in, so its content could not be re-confirmed by a page fetch.From the public page text: the six domain names (Platform Overview and Navigation; Instance Configuration; Configuring Applications for Collaboration; Self Service and Automation; Database Management and Platform Security; Data Migration and Integration), 60 questions and 90 minutes. From the indexed page text: the weights 7% for Platform Overview and Navigation, 10% for Instance Configuration, 20% for Configuring Applications for Collaboration and 30% for Database Management and Platform Security.
The vendor does not publish this. ServiceNow's public blueprint text shows four of the six domain weights, which add up to 67 per cent. The remaining 33 per cent is split here as 20 per cent for Self Service and Automation and 13 per cent for Data Migration and Integration; those two figures come from secondary study sources that agree with each other, not from a page we could read ourselves. ServiceNow does not publish a cut score, so the exam is reported as pass or fail with no official passing percentage.