Overview

Every user has a global role for the workspace and a role in each team they belong to. Inside a team, the team role applies.

Global roles
Global Admin, Stakeholder
Team roles
Team Manager, Responder, Observer, SLA Tracker
In a team
The team role applies

How global and team roles combine

  • Global Admin and Stakeholder are global roles. Inside a team, a Global Admin acts as a Team Manager and a Stakeholder as an Observer.
  • Team Manager, Responder and Observer are team roles. You can also give one as a global role to limit what someone can do across the workspace.
  • SLA Tracker is both. Only users who are SLA Trackers globally can be SLA Trackers in a team.
  • Inside a team, the team role takes priority over the global role.

What each role can do

Can Global Admin Stakeholder Team Manager Responder Observer
Invite new users to the workspace Yes
Create or delete teams Yes
Add existing users to a team, change team roles Yes Own team
Create, acknowledge, resolve, reassign incidents Yes Own team Own team
View incidents Yes Yes Own team Own team Own team
Create, edit, delete schedules, services, escalation policies, API tokens Yes Own team
Create schedule overrides Yes Own team
View schedules, escalation policies, services Yes Yes Own team Own team Own team
Reports and logs All All except user report Own team Notification log, incident report Notification log, incident report, API log, email log
Projects, team response thresholds Yes Own team
Voice, IVR, language, SLAs, organization settings, incident priorities, global thresholds Yes

SLA Tracker

For people who follow SLA performance, such as a product manager. An SLA Tracker can see incidents from any team that affect an SLA when their team is that SLA's escalation team, see those SLA reports, and work on incidents in their own team. See SLA.

Stakeholders and Observers can receive incident notifications when they are assigned or in an escalation policy, but can only view incidents, not act on them.