Admin
Configures identities, service ownership and access for the operating team.
Can
- Manage Users, People, Services
- View log streams, log alerts, Incidents, Changes, Problems, service requests, integration receipts
Assign service decisions and record access to the right people.
Connect each person to a user account before assigning incidents, problems or service ownership.
A Change Approver reviews risk and rollback before implementation; a Request Approver decides whether submitted work may proceed.
Log Operators register streams and triage alerts; Incident Responders own incident updates.
Service Owners can inspect the work tied to the services they operate.
| Role | Services and log streams | Log alerts | Incidents and updates | Changes | Problems and assets | Requests and receipts |
|---|---|---|---|---|---|---|
| Admin | Edit | View | Edit | View | Edit | Edit |
| Service Owner | Edit | View | View | View | Edit | View |
| Log Operator | Edit | Edit | View | — | — | View |
| Incident Responder | View | View | Edit | — | View | — |
| Change Approver | View | — | View | Approve | View | — |
| Request Approver | View | — | View | — | View | Approve |
| Request Fulfiller | View | — | View | — | View | Edit |
Configures identities, service ownership and access for the operating team.
Owns service context and reviews incidents, alerts and problems affecting that service.
Starts on: Change schedule
Registers streams, reviews alerts and examines inbound processing outcomes.
Starts on: Processing receipts
Acknowledges assigned incidents and records investigation updates.
Starts on: Incident queue
Reviews the risk, window and rollback plan before authorizing a change.
Starts on: Change schedule
Decides whether a submitted service request may proceed.
Starts on: Submitted requests
Carries approved service requests through execution and completion.
Starts on: Request fulfillment
Start free, then use Proto to change fields, steps and approvals before your team goes live.