Info |
---|
To know more about the Operations global admin role, please refer this page |
Teams are built up of users. A user can be a member of multiple teams. Even users that don't have a Compass license can be a member of a team that’s equipped to manage operations. Such users should be first invited to Compass. Members may also be given specific roles on a team.
For example, some users may be granted additional permissions to handle specific administrative tasks for the team (managing on-call schedules and escalations, etc.).
This article is about how you can manage the roles of your team members that deal with operations. There are only two basic roles any member of your team can hold within the operations space: Team admin and User.
Team admin
Members of your team that take this role can manage any kind of You can manage the member roles in Operations at two levels:
Global level
Operations global admin
User
Custom (only available in Premium and Enterprise)
Team level
Team admin
User
Custom (only available in Premium and Enterprise)
The following section describes each role.
Operations global admin
An Operations global admin is a user who configures all the operations-related settings at the global level. This role provides all administrative privileges specifically for Operations capabilities for all teams on your site, setting it apart from the Product admin role for the Jira administration.
Only a Product admin and an Operations global admin can assign this role to other users. Read more about the Operations global admin role.
Team admin
A user who has the role of a team admin can manage any settings, configuration (schedule configuration, integration setup, etc.), and other users in the team. Anyone on the team can be a team admin - the admin—the role assignment can happen either when you’re setting up operations/alerting for your team (for example, you can make someone with access to Compass a team admin at this step itself) or afterward too.When
If you are a:
Product admin for Jira administration and added to a team,
...
you automatically become a team admin
...
.
Product admin for Jira administration but not a member of a team, you can still configure a team's operations. However, you don’t have permission to manage the members of that team.
User
Default users A user’s role is present at both the global and team levels. A default user can only access the configurations that they're part of, and they can only access the alerts that for which they have permission for. In other words, a default users user can manage the settings that will only affect themselves.
Roles and permissions matrix
...
Custom roles
Custom roles are a way to customize the capabilities of the users in a team that handles operations by granting or revoking the permissions of your choice. Custom user roles are only available in the Premium and Enterprise plans of Jira Service Management. Read more about custom roles.
Roles and permissions matrix
The following table lists the associated permissions for each role:
Permissions | Operations global admin | Team admin | User |
---|
Add or remove team members
✔
Create/Edit/Delete routing rules of the team
✔
Create, edit, or delete Operations configurations for the entire site | ✔ | ||
Create, edit, or delete Operations configurations for the team | ✔ |
Create/Edit/Delete integrations for the team
✔ | |
Access escalations, schedules, and integrations of the team | ✔ |
✔ | ✔ |
Access the team's dashboard | ✔ |
✔
(only if added to the team) | ✔ | ✔ |
Access all alerts assigned to the team | ✔ (only if added to the team) | ✔ |
Integrations and on-call pages
✔ |
✔
...