Overview
Create and manage service events for your status dashboards.
Events are how your team communicates service disruptions, planned maintenance, and general notices on your status dashboards. In the admin console, you create and manage each event through a structured editor with tabs for status, timing, components, and publication.
The pages below explain the event editor and the organization settings that shape how incidents and maintenance behave.
Event editor
Events are the primary way you communicate with your users during a service disruption, planned maintenance, or to share a general notice. Each event has a type that determines its behavior, a lifecycle driven by a timeline, and can be published to your status dashboards.
The event type is set at creation and cannot be changed. See Incidents, Maintenance, and Informational for details on each type.
When you create or edit an event, the form is organized into sections to help guide you in management of the event.
| Tab | Documentation |
|---|---|
| General | Choose the event type, set the title, and view the current status. Incidents · Maintenance · Informational |
| Timeline | Post public status updates; re-open resolved incidents. Timeline |
| Date & Time | Set start and end times; configure automatic maintenance start and stop. Incidents — times · Maintenance |
| Components | Select affected components and assign per-component severity. Severity levels |
| Description | Write the public-facing summary shown on status dashboards. Incidents and maintenance also support an optional Impact Analysis field for customer and service impact details. |
| Coordinator | Assign a point of contact displayed on the status dashboard. Coordinator |
| Notifications | Control whether subscribers receive email or SMS when the event changes. Notifications |
| Segments | Include or exclude notification recipients by audience segment. Segments |
| Attributes | Attach custom key/value metadata with public or private visibility. Attributes |
| Notes | Track internal context for your team that is never published. Notes |
| Publish | Control whether the event is visible on your status dashboards. Publish |
| Post-Mortem | Document root cause, impact, and remediation tasks after the event is resolved. Post-Mortem |
Related configuration that affects event behavior: