ServiceNow Certified System Administrator (CSA)

Many organizations run ServiceNow on admins who learned by clicking around. That can lead to inconsistent forms, ACLs nobody can explain, and changes made without a shared understanding of the platform. This course gives your team a structured foundation for administering ServiceNow and preparing for the Certified System Administrator (CSA) exam.

Role fit: The course suits junior admins, help-desk leads, and analysts who already maintain ServiceNow. Team Leads can assign it to everyone who approves catalog items, edits forms, or troubleshoots access. It also covers JavaScript, GlideRecord, business rules, and client scripts, so IT Practitioners without a scripting background get the basics they need before automating anything.

Time investment: Plan for about 37 hours across 47 skills. Most skills run under an hour, so learners can fit them into the work week without long stretches away from their queues.

Risk and change management: The course teaches admins to:

• Understand ServiceNow’s data model, tables, and records before making platform changes.
• Design and debug ACLs and conditional ACLs so the right people see the right records.
• Work with service catalog tables and records that support automated request and approval workflows.

These habits help reduce inconsistent admin work and give your team a common way to think through ServiceNow changes.

How the training supports the outcome: Each skill includes challenge-and-solution exercises built on realistic scenarios, such as laptop provisioning flows, approval flows, and a training-feedback app secured with ACLs. Your team practices work they can apply directly in your own instance.

ServiceNow teams spend much of their week on the same requests: onboarding a new hire, getting a laptop to a remote worker, fixing access problems, and keeping knowledge articles current. This course works through those scenarios inside the platform. Your team practices the configuration and automation work that turns repeated manual effort into dependable, auditable processes.

• Faster, more consistent onboarding and fulfillment: Admins build Service Catalog items, Flow Designer flows, and subflows that move a laptop request from submission to delivery. They add approval steps where the business needs sign-off before work continues.
• Tighter, easier-to-troubleshoot access control: Using a training-feedback table as a working example, learners create roles and conditional ACLs so users can view and edit only their own records. They also practice debugging ACLs when access breaks.
• Safer change delivery: Your team learns to capture related configuration changes in update sets, review what changed, and apply those changes after testing. This helps reduce the risk of untested configuration affecting users.
• Less manual platform upkeep: Admins practice ServiceNow automation patterns that reduce repetitive data and process work, including scheduled jobs for recurring tasks. These jobs help cover gaps that business rules and UI policies leave open.

The course also covers Visual Task Boards for tracking work ahead of deadlines and knowledge base design with user criteria. Together, these help your team see who owns each task and help users find answers without opening another ticket.

Knowledge

• How ServiceNow's core building blocks (tables, lists, forms, modules, and roles) fit together, and how table relationships shape the data your team works with every day
• Where automation logic belongs: when to use business rules, UI policies, client scripts, data policies, scheduled jobs, or Flow Designer flows and subflows
• How the import pipeline works, from data sources and staging (import set) tables through transformation, including when custom scripts are needed for non-standard file formats
• How access control works: user roles, application and module roles, ACLs, and knowledge base user criteria
• How the task lifecycle, approvals, and Service Catalog requests connect into end-to-end fulfillment, such as getting a laptop to a new or remote employee
• What update sets capture and what they don't, and why records like users and incidents belong on production rather than dev

Ability

• Administer tables, lists, forms, filters, tags, and Visual Task Boards to track work and prepare for deadlines
• Write JavaScript and GlideRecord scripts for business rules, including error handling with try-catch and object-based field population
• Build approval flows and catalog automation that route requests to the right people
• Create and secure knowledge bases with categories, article templates, and role- and criteria-based access
• Configure ACLs and debug access issues when users can't see or edit records
• Build and test changes on a dev instance, then promote them to production with update sets