Skip to content
Tutorials Center
My learning

Topics

Lesson 7 of 39 ยท Platform and Navigation

Users, Groups and Roles

Understand sys_user, sys_user_group and roles: how members inherit roles, contained roles, the itil and admin roles, impersonation and elevated privileges.

Who may see an incident? Who may approve a change? ServiceNow answers with users, groups and roles. Getting this model right is the foundation of administration, and it feeds directly into access control (ACLs) later in the course.

The three building blocks

  • A user is a record in sys_user: name, user ID, email, department, manager, location, active flag.
  • A group is a record in sys_user_group: a set of users who share work, such as Service Desk or Network Support. Membership is a record in sys_user_grmember.
  • A role is a record in sys_user_role: a named permission such as itil or admin. Granting a role is a record in sys_user_has_role (for a user) or sys_group_has_role (for a group).

Assign roles to groups, not to individuals, whenever possible. When someone moves teams you change their group membership and their access follows.

How access reaches a user

User A record in sys_user.
Group Members share work.
Role A named permission.
ACL Checks the role on each action.

Give roles to groups, then add people to groups.

1 / 2

Common roles

Role Typical meaning
admin Full system administrator. Can do nearly everything.
itil A fulfiller: works incidents, problems and changes
itil_admin Administers the ITSM processes
snc_internal Any internal (employee) user
snc_external An external user
approver_user Can approve requests
catalog_admin Manages the service catalog
security_admin Elevated role needed to edit security rules such as ACLs

Role names follow the platform's history, so some look odd. Always check the role record's description.

Contained roles

A role can contain other roles (the Contains roles related list). Holding the parent gives you the contained roles. itil_admin, for example, contains itil. A user's effective roles are everything granted directly, through any group, and through containment.

Python Effective roles (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Creating a user and a group

  1. Open User Administration > Users (or the list sys_user.list) and press New.
  2. Fill User ID (the login name), First name, Last name, Email, and set a Password only if the instance uses local authentication (most companies use SSO).
  3. Keep Active checked, then Submit.
  4. Open User Administration > Groups, press New, give a Name, a Manager if wanted, and Submit.
  5. On the group form, open the Group Members related list and add the user, then open Roles and add itil.

The new user now holds itil through the group. To prove it, use Impersonate user from the user menu and open the Incident list.

Impersonation and elevated roles

Impersonate user (admin only) lets you see the system as another user; it is the quickest way to debug "I cannot see the button" tickets. Everything you do is audited under the impersonated user, so use it carefully on real instances and stop impersonating afterwards.

Some actions, such as editing ACLs, require the security_admin role. Admins do not hold it permanently; they choose Elevate role in the user menu and confirm. The elevation lasts for the session and shows in the header.

Good practices

  • Use group roles, keep groups small and meaningful, and document each group's purpose.
  • Deactivate users instead of deleting them, so historical records keep their references.
  • Review the admin role: grant it sparingly.
  • Use User Administration > Roles to audit what a role contains.
  • Prefer built-in groups and roles for out-of-the-box processes, and create custom roles (named with your company prefix) for custom apps.
Python Audit: users with admin (stand-in)

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why assign roles to groups rather than individuals?

    When people change teams you edit membership and their access updates automatically.
  2. 2. What does a contained role do?

    A role can include others, so holding it grants all of them.
  3. 3. Which role is typically elevated to edit ACLs?

    Editing security rules needs security_admin, which admins elevate into temporarily.
  4. 4. Which is better for a leaver?

    Deactivating keeps historical records and references intact.

Summary

  • Users, groups and roles live in sys_user, sys_user_group and sys_user_role.
  • Give roles to groups; roles can contain other roles.
  • Admins elevate to security_admin for security changes and impersonate to debug.
  • Deactivate rather than delete users.

Next: Scoped Applications and Update Sets