...
Team admin | Members of 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 with access to Jira Service Management a team admin at this step itself) or afterward too. When added to a team, a Jira admin is assigned a team admin role by default. Jira admins can also configure a team even if they are not a member of the team. |
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. |
...
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 | ✔ | ✔ |
Integrations and on-call pages | ✔ | ✔ |
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 configurationsNon-admin users typically only have read-only permissions on these pages.