Teams are built up of users. A user can be a member of multiple teams. Even users that don't have a Jira Service Management license can be a member of a team that’s equipped to manage operations. Such users should be first invited to Jira Service Management. Users may also be given specific roles on a team. For example, some users may be granted additional permissions to handle certain administrative tasks for the team.
This article is about how you can manage the roles of your team members that deal with operations. There are only two roles members in your team can hold within the operations space: Team admin and User.
Team admin | Members on your team that take this role can manage any kind of settings, configuration (schedule configuration, integration setup, etc.), and other users in the team. Anyone on the team can be a team admin - the role assignment can happen either when you’re setting up operations/alerting for your team (for example, you can make someone who has access to Jira Service Management a team admin at this step itself) or afterwards too. A Jira admin when added to a team is assigned a team admin role by default. |
User | Default users can only access the configurations that they're part of, and they can only access the alerts that they have permission for. In other words, default users can manage the settings that will only affect themselves. |
Permissions matrix
Team admin and User are the two predefined team roles that Jira Service Management provides for your team. The following table lists the associated permissions for each role.
Activity | Team admin | User |
|---|---|---|
Add or remove team members | ✔ |
|
Create/Edit/Delete routing rules of the team | ✔ |
|
Create/Edit/Delete escalations for the team | ✔ |
|
Create/Edit/Delete schedules for the team | ✔ |
|
Create/Edit/Delete integrations for the team | ✔ |
|
Access team's dashboard | ✔ | ✔ |
Access escalations, schedules and integrations of the team | ✔ | ✔ |
Access all alerts assigned to the team | ✔ | ✔ |
When a team admin that does not have an “edit configuration” permission at a site level adds an escalation, schedule, or integration, the configuration is automatically assigned to the team they are admin for. You can refer to the Teams and Team Segmentation for further information about the teams and their configurations.
0 Comments