> ## Documentation Index
> Fetch the complete documentation index at: https://docs.use.observer/llms.txt
> Use this file to discover all available pages before exploring further.

# Subscriber notification events

> Which incident and maintenance transitions notify status page subscribers, by email, Slack, Teams, or webhook.

When an incident or maintenance window changes, Observer notifies the
confirmed subscribers of every page it appears on. The same rules apply to
every subscriber channel: email, Slack, Microsoft Teams, and webhook. The
matrix below lists which event types notify subscribers.

## Trigger matrix

| Event | Notifies subscribers |
| - | - |
| `incident.created` | No (draft state). |
| `incident.published` | Yes. |
| `incident.updated` | No (avoids notification spam on minor edits). |
| `incident.message_added` | Yes, once the incident is published. Messages on a draft never notify. A **Resolved** message that closes the incident notifies once, as `incident.resolved`. |
| `incident.resolved` | Yes. |
| `incident.deleted` | No. |
| `maintenance.scheduled` | Yes, when the maintenance is published. |
| `maintenance.starting_soon` | Yes (one hour before the scheduled start). |
| `maintenance.started` | No (the starting-soon notification covered it). |
| `maintenance.completed` | Yes. |
| `maintenance.canceled` | Yes. |

Webhook subscribers receive these as JSON; see the
[subscriber webhook reference](https://docs.use.observer/docs/reference/subscriber-webhooks.md) for the
payloads.

## Filter scopes

When a subscriber has chosen specific services or metrics, an update reaches
them when at least one of its affected services, or a metric behind one of
those services, is among their selection, or when the update names no
affected services (a page-wide update).
Subscribers who chose no filters receive every relevant event for the page.

Recoveries always deliver: `incident.resolved`, `maintenance.completed`, and
`maintenance.canceled` reach every subscriber who was notified earlier about
the same incident or maintenance, even if its affected services changed in
between.

## Customer-scoped incidents

Customer-scoped incidents reach only subscribers tied to the listed
customers. Alerts destinations are not filtered by customer scope: a
destination receives the incident when it is org-wide or scoped to one
of the incident's pages.

## Per-attempt audit

Every send is recorded per subscriber and event, so an event is not sent
twice to the same subscriber. The console **Subscribers** view lists each
subscriber's subscription status (confirmed, unconfirmed, or unsubscribed),
not individual delivery outcomes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.