🧙🏿♂️ Incident roles
What are roles?
Purpose of Roles: establish shared, clearly defined roles and responsibilities so everyone in the company knows who should be doing what during an incident and team members can delegate and fulfill their own roles effectively.
Think:
- an incident commander who runs the incident
- a comms lead who communicates updates about an incident internally and externally
- a participant who simply collaborates to resolve the ongoing incident
What are the default roles?
Default roles vary by 🔀 Workflows. The default roles for Allma’s technical incident workflow are as follows:
Incident commander
The primary decision maker for the incident, listening to hypotheses and data presented by participants and delegating actions.
Communications lead
The core communicator for the incident, conveying status, updates, and technical details to stakeholders, support personnel, and/or customers.
Participant
Team member available to investigate, carry-out actions delegated by the Incident Commander, and actively work towards incident mitigation.
Watcher
Team member with knowledge or guidance that might contribute to resolution, but is not available to actively investigate or carry-out mitigative actions.
Do roles have corresponding functionality tied to them?
Yes, the actions a collaborator can perform within an incident may be limited by the configuration of their role. For more information, see 🗝️ Workflow role permissions.
Note: users without roles have a default set of permissions. See 🎩 Default incident permissions for more details.
Can I change my role during an Incident?
Yes, you can always re-assign or change roles throughout an incident. You can do so by executing the slash commands /allma role (change your role) and /allma assign (assign a role). Or by clicking the buttons in the incident channel: "Change My Role" and "Assign Role."