The delivery log and the bell
Two places show you what your alerts actually did: the bell (for everyone, in the moment) and the delivery log (for admins, the full record).
The bell
The bell in the top bar is visible to everyone in your workspace and combines two things:
- Connection alerts — anything currently broken: a mailbox or integration that needs reconnecting, with a link to Settings. These stay until the connection is fixed.
- Notifications — your in-app alert feed: every alert delivered in-app, plus any alert email that failed to send (so a silent email failure still surfaces). Routine successful emails don’t clutter the bell — they’re in the delivery log.
Click a notification to jump to the email behind it in Inbox activity. Mark all read clears the badge. Read state is shared across the workspace — when a teammate marks something read, it shows read for everyone. Members see notifications for the mailboxes they have access to; workspace-wide alerts (like a disconnection) show for everyone.
The delivery log
The Delivery log tab on the Notifications screen (admins only) is the complete audit of every alert fired: when, which rule, which event, which channel, who received it, and whether it succeeded. Failed email deliveries show the error inline.
Filter by status (Success / Failed), channel (Email / In-app), or event. It’s read-only — there’s no re-send; if an email failed, fix the cause and the next event will deliver normally.
”Why didn’t I get an email?”
Checklist, fastest first:
- Delivery log — did the alert fire at all? If yes with Failed, the error text says why.
- If it fired successfully but isn’t in your inbox — check spam/quarantine on your side.
- If it didn’t fire: is the toggle/rule Active? Are you on the recipients? Does a custom alert’s Min Confidence or condition exclude the email?
- Remember alerts fire per decision — an email that was skipped as noise sends no alert.