Reference tables
Reference
Severities
| Severity | Use |
|---|
| Critical | Highest-priority incident |
| High | High-severity incident |
| Warning | Medium-severity incident |
| Info | Lower-severity informational incident |
Escalation timing and notification paths can be configured separately for each severity.
Incident states
| State | Meaning |
|---|
| Active | The incident has been raised. |
| Acknowledged | Someone has taken ownership. |
| Escalating | No acknowledgement occurred within the configured time. |
| Resolved | The incident has been closed. |
Roles and permissions
| Action | Admin | Member |
|---|
| View incidents | Yes | Yes |
| Acknowledge incidents | Yes | Yes |
| Resolve incidents | Yes | Yes |
| View configuration | Yes | Yes |
| Change Shankh configuration | Yes | No |
| Manage workspaces, teams and members | Yes | No |
| Configure alerting | Yes | No |
| Configure escalation | Yes | No |
| Configure cloud integration | Yes | No |
Notification channel availability
| Channel | Incident delivery |
|---|
| Slack | Supported |
| Telegram | Supported |
| Mobile push | Supported |
| WhatsApp | Not currently available |
| Voice calls | Not currently available |
| SMS | Not currently available |
| Email | Not currently available |
Some unavailable channels may still appear in parts of the interface. Do not use them as production escalation channels until delivery is enabled.