Everyday response#
| Area | Use it to |
|---|---|
| Overview | Review the current incident picture and operational context, and schedule or end maintenance windows. |
| Incidents | Open a response record, inspect its timeline, acknowledge, resolve, add notes, publish status updates, open a ticket, or take permitted response actions. |
| Alerts | Inspect normalized monitoring conditions and repeated occurrences. |
| On Call | Inspect coverage and current responders; organization admins can configure schedules. |
| My Shifts | See your upcoming shifts, ask for or offer cover, and create a calendar feed. |
| Postmortems | See which incidents owe a review and write or read postmortems. |
Configuration#
| Area | Use it to |
|---|---|
| Services / Teams | Understand and manage ownership, runbooks, escalation relationships, stakeholders and chat channels. |
| Escalation Policies / Routing Rules | Decide who is reached and which service owns an alert. |
| Integrations / Heartbeats / Webhooks | Connect monitoring sources, page on silent jobs, and send incident events to your own systems. |
| Stakeholders / Status Pages | Keep people who are not paged informed. |
| Call Routing / Ticketing | Connect a hotline number, and open Jira or Halo tickets from incidents. |
| Notification Providers | Configure the organization's delivery channels and run provider tests. |
Administration#
| Area | Use it to |
|---|---|
| Reports | Review incident, acknowledgement and paging trends per service, team and person. |
| Users / API Keys / RBAC | Manage people, automation tokens and role-based access. |
| Identity | Configure single sign-on, directory sign-in, group mappings and SCIM provisioning. |
| Audit | Review, export or stream organization-scoped configuration and response actions. |
| Delivery Health | Inspect processing failures, quarantined events, and notification problems. |
| Setup / Settings | Inspect guided onboarding progress, and manage organization settings such as timezone, default severity and postmortem expectations. |
Refresh, permissions, and stale state#
The backend is authoritative. An acknowledgement is successful only when the API confirms it. Concurrent actions may return a conflict; refresh the incident and inspect its new version before retrying. Hidden controls do not grant access, and a visible URL cannot bypass backend authorization.