Settings

Notifications

Routing isn't configured yet
A notification with no named recipient is a notification nobody reads. Every route here points at people, not at "the team" — so when a production deploy fails at 2am it goes to Ren, and when a card is declined it goes to the person who can fix a card.
When this happensTell these people, this way

No notification routes yet

Routing events to people and channels is not stored anywhere yet, so there is nothing to list. Your own inbox keeps working as before.

Who's carrying the pager

Routes per person, so nobody is silently on the hook for everything

Loading people…

Noise controls

Applied after routing, before sending

Batch routine events hourlyComments and approvals arrive as one digest.Not stored yet
Quiet hours 22:00 – 07:00Critical routes ignore this.Not stored yet
Escalate unacknowledged criticalsAfter 30 minutes, also notify the workspace owner.Not stored yet
One message per incident, not per retryA flow that retries 5 times sends one alert.Not stored yet