Notifications

Across every product, the platform emits a notification when something happens that a person should hear about: a Stacks run is waiting for approval, a payment failed, an invoice is ready, an on-call schedule changed. Notifications are informational — they tell you that something happened and link you to it. They are not paging: an on-call page is a separate, louder mechanism that keeps working even when the Console is down.

Where notifications go

Every notification lands in two places you can always read, and — if you ask for it — reaches you off-platform.

• Your organization’s feed — everything scoped to your Org, newest first, under Organization → Notifications. It’s a browseable feed, filtered to the products you can read: you see notifications for the services your access covers, nothing more.
• Your personal inbox — notifications addressed to you (an invitation, something you subscribed to), under Profile → Notifications and the bell in the sidebar. The bell shows an unread count; your inbox tracks what you’ve read.
• Email and Slack — off-platform delivery you opt into (below). Some important notifications email you by default.

Loud and quiet

Each kind of notification belongs to a group — “Billing — account issues”, “Billing — receipts”, and so on — and every group is either loud or quiet.

• Quiet groups (most of them — receipts, routine progress) appear in the feeds but don’t email anyone unless someone subscribes.
• Loud groups (payment problems, account suspension, security notices) email your Org’s owners automatically, and — for billing — your Org’s billing contacts. An owner can mute a loud group they’d rather not be emailed about.

Being the direct subject of a notification — an invitation to you personally — always reaches you, inbox and email, regardless of these settings.

Choosing what reaches you

Personally (Profile → Notifications): opt in to email for a quiet group you care about, or mute a loud group you don’t want emailed about. Everything still shows up in your inbox either way.

For a Slack channel (Organization → Notifications): an org admin adds a channel by pasting a Slack incoming-webhook URL — it’s stored write-only, so it’s never shown back — then subscribes it to the groups it should hear. A subscription can be narrowed to a single resource, so, for example, #infra-prod hears only your production stack’s failures.

Retention

Notifications are news, not a permanent record: they’re kept for 90 days. Your durable history lives elsewhere — the audit log for who did what, and your invoices for billing.