Two surfaces, and the split between them is the same one your working life has: what you want to hear about depends on the workspace, when and how you hear about it does not.
The Preferences tab of the notifications page lists every kind of notification against every channel. Each cell is one of:
| Mode | Effect |
|---|---|
| Immediate | Sent as soon as it happens (email still waits out its short cancel window) |
| Digest | Held and rolled into your next digest — email only |
| Off | Nothing at all on that channel |
Not every channel offers all three. In-app is on or off, because it is never rolled up; so is the webhook, because a machine integration that arrives tomorrow morning in a batch is not one.
Switching in-app off for a kind of notification means no row is written for you, ever. It is a real off switch, not a quieter setting — which is what makes a chatty flow genuinely silenceable.
These choices are per workspace. Being on call for production and a spectator in a colleague's sandbox is the normal case, and the matrix is where that gets expressed. The handful of notifications that are about you rather than about a workspace — your role, your removal, your tokens, your webhook being disabled — are configured once and apply everywhere.
One person has one timezone and one sleeping pattern, so these live on your account rather than being asked again in every workspace.
A switch in the matrix turns off a whole kind of notification. A mute turns off one specific flow, deployment or connection while leaving the rest of that kind alone — the right tool for the one integration that is always half-broken, or the one deployment being deliberately hammered in testing.
Mute from the row itself: any notification in the inbox offers to silence the resource it came from. Muting picks the narrowest thing the row names — the connection if it has one, otherwise the deployment, otherwise the flow.
Mutes are personal: yours silences your inbox and nobody else's. They are listed on the Muted tab, and unmuting takes effect from that moment — nothing that was suppressed while the mute was in place is backfilled.
Notifications addressed to you personally cannot be muted, because there is no resource to attach the mute to.
Preferences decide what reaches you out of what you are eligible for, and never widen that. If your permissions do not let you read a workspace's executions, no setting on this page will send you its deployment failures — see Your inbox.