ServiceNow Administration Basics

The lesson explains the ServiceNow admin role through a building manager metaphor and introduces the key terms instance, application, and module. It also walks through setting up a developer instance, impersonating users to test permissions, and adding frequent admin tasks, such as creating and maintaining catalog items, to Favorites.

The trainer assumes learners already know the basics of ServiceNow, including its core interfaces and terminology, and recommends his separate ServiceNow basics course first. Training Managers onboarding help desk staff or junior admins who are new to the platform can sequence that foundation ahead of this lesson.

The lesson runs 47 minutes and opens the beginner-level course, which spans 16 lessons totaling about 13 hours per learner. It sets up the terminology and the developer instance that later lessons on users and roles, ACLs, tables, forms, workflows, service catalog, update sets, and reporting build on.

Making a change that takes effect immediately across the organization is usually a bad idea, so admins experiment in a dev sandbox, test in QA, and only then release to production, the instance everyone uses. For Team Leads, this gives a consistent model for governing platform changes before handing out broader admin responsibility.

Log in at developer.servicenow.com, request an instance, and open it, where you are signed in as a system administrator and can make changes without risk to the organization's instance. Because sleeping instances take about 15 to 20 minutes to wake, the trainer recommends waking it at the start of each working session.

Other users see a completely different interface than an admin, so impersonation lets the admin verify exactly what a user sees when setting up permissions and access control. It is a practice used throughout the course and supports the access governance work covered later with users, roles, and ACLs.