Admin
Configures users, people and service ownership.
Can
- Manage Users, People, Services
- View integration receipts
Assign service, incident and communication decisions to named people.
Connect each service to the person responsible for its operating status.
A message reviewer should check incident facts and audience before publication; a change decision should happen before implementation.
Give each team member access to the records required by their assignment, then check what another role can open.
| Role | Services and components | Incidents | Public communication | Changes and maintenance | Requests and problems | Assets and receipts |
|---|---|---|---|---|---|---|
| Admin | Edit | Edit | Edit | — | Edit | View |
| Service Owner | Edit | View | Edit | Edit | View | Edit |
| Incident Coordinator | View | Edit | Edit | View | — | View |
| Communications Reviewer | View | View | Approve | View | — | — |
| Change Manager | View | View | — | Approve | — | — |
| Request Manager | View | View | — | — | Edit | — |
Configures users, people and service ownership.
Maintains the service catalogue and reviews service-specific work.
Starts on: Change schedule
Opens incidents, assigns investigation and records recovery.
Starts on: Open incidents
Reviews incident-linked messages for the stated audience.
Starts on: Component status board
Reviews planned service changes and their rollback context.
Starts on: Change schedule
Tracks requested work and recurring problems for a service.
Starts on: Current problems
Start free, then use Proto to change fields, steps and approvals before your team goes live.