Notifications

Notification routing connects a project or endpoint to verified contact methods. Configure it before an incident. The first actionable signal can then reach the right responder.

Add a contact method

Open Contact methods. Add an email address. Complete verification. An unverified or disabled contact method cannot receive operational delivery.

Use a label that explains the destination, such as Primary on-call or Platform team. Do not repeat the email address in the label.

Choose the scope

Team editors manage subscriptions for each team member. A subscription can apply to a project or to one endpoint:

• Subscribe at the project level when the same people own every endpoint in that project.
• Subscribe at the endpoint level when a service has a specialist owner or escalation path.

Endpoint recipients can include people who inherit the project subscription. Review both scopes when you audit delivery.

Read notifications

Open My Updates to review in-app records. You can filter by unread state, category, severity, project, endpoint, or exact type.

Select a notification to open its related record when it has one. Mark one item as read. You can also mark every notification as read.

Keep routing useful

• Route critical services to a contact method that someone actively monitors.
• Remove subscriptions when ownership changes.
• Keep project boundaries aligned with responder ownership.
• Review notification history after a test or incident.

Related guides

• Manage teams and access
• Investigate incidents