Roles and permissions
Service Management has built-in roles that are based on industry best practice recommendations. Large companies might have several people assigned to the same role. Smaller organizations might have multiple roles assigned to one person. Maintaining a role-based view of the organization makes sure that you adhere to the best practice model no matter who is assigned to the role or how you divide the responsibilities associated with the role. For example, if your company is large, you may have separate process designers and process owners assigned to each module. A smaller company might assign both roles to one person for each module.
Roles have certain permissions that enable you to complete your daily work. Roles are assigned by application area. For example, an Incident Coordinator, Change Coordinator, and Problem Coordinator are similar roles with similar rights within the Incident, Change, and Problem Management applications.
Permissions are controls within applications. When assigned, they enable you to complete certain Service Management tasks, such as adding update information to a record. Permissions are an administrative strategy to control access to records and limit the number of people who can view, create, update, or delete records. Permissions to view particular data domains limit your ability to view only records that are tagged with those domains.
For more information, see Data domain segmentation.
If you are not familiar with the permissions assigned to you or your role, contact your tenant administrator.
If you are not familiar with your assigned role, contact your tenant administrator.
Note A license is required to log into Service Management. For more information, see How to assign licenses to users.