In ServiceNow,rolesdefine the level of access a user has within an instance.Roles are stored in thesys_user_roletable.
Definition of a Role:
Aroleis a collection ofpermissionsthat grant access to different parts of the system.
Example:Theadminrole grants full access, while theitilrole allows incident management access.
sys_user_role Table:
This tablestores role recordsand their associated metadata.
Every role has aunique sys_id, aname, and may be associated withparent roles(role inheritance).
Users are linked to roles through thesys_user_has_roletable.
How Roles Work in ServiceNow:
A user assigned a role gainsall the permissionsassociated with that role.
Roles can behierarchical(one role can inherit permissions from another).
Example:Theitil_adminrole includes all the permissions of theitilrole, plus additional privileges.
Key Details About Roles and sys_user_role Table:Why Option D (sys_user_role) Is Correct?sys_user_role→ The correct table where roles are recorded in ServiceNow.
Why Other Options Are Incorrect?A. sys_user→ Incorrect; this table stores user records, not roles.
B. sys_user_profile→ Incorrect; this table does not exist in ServiceNow.
C. sys_user_record→ Incorrect; this is not a valid table in ServiceNow.
ServiceNow Docs – Roles and Role Managementhttps://docs.servicenow.com
ServiceNow Table Schema – sys_user_role
ServiceNow Developer Portal – Role Hierarchy & Best Practices
References from Certified System Administrator (CSA) Documentation:
Submit