Notifications

In the app

The bell in the top bar shows your recent notifications, newest first, with unread ones marked. It refreshes on its own roughly every 45 seconds. Opening a notification takes you to the thing it is about, and you can mark everything read.

You only ever see notifications addressed to you, enforced by row level security rather than by filtering in the browser.

By email

Product email goes out through the platform's transactional sender. Delivery events are recorded, which is what lets an evidence-bearing message be shown to have been sent.

Choosing what you get

Notification preferences live on /app/settings, per workspace. There are two master switches, one for in-app and one for email, plus per-type mutes so you can turn off a single kind of notification without turning off everything.

If you have set no preference, you receive notifications. Absence of a preference row is treated as opted in, not opted out.

Fan-out is best effort

Sending notifications never blocks the action that caused them. If notification delivery fails, the underlying record, such as an expression of interest, is still written. The failure is logged for operators. The record is what matters; the message about it is not allowed to put the record at risk.

Some addresses never send

A few mailboxes, including legal, compliance, security and office, are for receiving mail from humans only. Nothing in the product ever sends automatically from them.