​

Notification digest vs. per-user preferences

Two settings pages decide what reaches your inbox and your email. Settings → Notifications (/settings/notifications) is your personal, per-category preference sheet. Settings → Notifications → Email Digest (/settings/notifications/digest) is the org-level roll-up an admin configures. Which one you reach for depends on which of these questions you are answering:

• “What lands in my email?” → your per-user preferences.
• “Does the org send a periodic summary at all, and who gets it?” → the org digest.

This FAQ walks each layer, then shows how they combine.

​

1. Per-user preferences (Settings → Notifications)

Your preferences are yours alone — they change nothing for other members. For each of six categories you control two things: Channel toggles — which delivery channels a category may use:

• Email — outbound email for that category’s events.
• Push — browser push.
• Webhook — the org’s webhook endpoint (fire-and-log kind only; see below).

Frequency — how outbound delivery is timed per category:

• Immediate — send as the event happens.
• Daily digest — batch into the next daily roll-up.
• Weekly digest — batch into the next weekly roll-up.

The categories: Billing (invoices, payment failures, plan changes), Security (sign-ins, API key events, suspicious activity), Messaging (delivery failures, number issues), Campaigns (completion, opt-out spikes, analytics), Agents (errors, escalations), System (maintenance, deprecations, outages). An Apply to all categories shortcut at the top sets one frequency across all six in a single click, and Save Preferences commits the whole form. Three things to know about how mutes behave:

1. In-app is never muted. Unticking every channel only stops outbound delivery. The in-app bell row is still minted for every event, so muting is not the same as blinding yourself — you can always catch up in the Notification Center.
2. A frequency is a request, not a guarantee of a second send. A category set to immediate fires right away and is never re-batched into the roll-up.
3. Webhook is a fire-and-log kind. It mirrors the event to your endpoint; it is not an interactive preference the way email and push are.

​

2. Opting in and out of the org digest

The digest is opt-in at two levels, and both must be on before any summary email leaves:

• Org master toggle — an admin flips Enabled on the digest page. Off means no digest emails for anyone, whatever the recipient list says.
• Per-member opt-in — the Recipients list on the same page holds one switch per member. Only members switched on receive the digest. Admins are switched on by default; everyone else starts opted out.

To opt yourself in or out, ask an owner or admin to flip your row in Settings → Notifications → Email Digest → Recipients. Because the recipient registry is admin-managed, a member who never had their row toggled on gets nothing — the org does not silently subscribe the whole team. Opting out drains your pending roll-up rows without sending, so you stop receiving from the next cycle, not after a backlog flushes.

​

3. Where admins configure cadence and categories

Org-level digest settings live at Settings → Notifications → Email Digest (/settings/notifications/digest), also linked from the Email Digest card at the bottom of the main Notifications page. Writes are admin-gated; viewers see the page read-only. The page exposes four controls:

• Enabled — the org master toggle described above.
• Frequency — Daily or Weekly. One email per opted-in member per cycle, covering every category that member opted into. The scheduler also enforces a minimum interval, so a late tick cannot double-send inside the window.
• Included categories — which of the six categories the digest may cover. An empty selection means all categories; uncheck the ones you want excluded.
• Preview next digest — computes the payload (per-window counts of campaigns sent, messages delivered/failed, conversations started, agent runs, spend, plus highlights) without emailing anyone. Use it before enabling to check the roll-up is not empty and contains what you expect.

The full page guide, including the API surface (GET/PUT /api/v1/notifications/digest/settings, GET/PATCH …/recipients, POST …/preview), is in Triage the Notification Center.

​

4. Security categories always fire

Security-notification kinds — new sign-in from an unknown IP or device, password and email changes, two-factor changes, API key creation or revocation, member role changes — are delivered regardless of your channel mutes and regardless of category inclusion in the digest. A suppressible security preference would let a hijacked session mute the takeover signal, so the platform does not offer one. Muting stops routine noise only.

​

5. Worked examples

Mute campaigns, keep billing. Open Settings → Notifications, find the Campaigns card, untick Email, and save. Campaign events still mint in-app bell rows; billing email arrives as before. Everything as a weekly roll-up. Use the Apply to all categories shortcut, pick Weekly digest, save. Your outbound email now lands in one weekly summary per category you left enabled — provided the org digest is on and you are opted in. Disable the digest org-wide. An admin opens Settings → Notifications → Email Digest and switches Enabled off. Per-user preferences are untouched — members keep whatever channel and frequency settings they had; the roll-up simply stops sending. Opt a single member out. An admin flips that member’s row in Recipients. Every other opted-in member keeps receiving; the opted-out member’s queue drains without a send. Keep security, mute everything else. Untick all channels on every category. Security events still reach you (they ignore mutes); the rest remain readable in the Notification Center.

​

Troubleshooting

• I set a category to daily but no digest arrived. Check, in order: the org digest Enabled toggle, your row in Recipients, and that the category is not excluded under Included categories. All three gates must pass.
• My frequency is immediate — why did nothing batch? That is expected. Immediate delivery fires at once and is intentionally excluded from the roll-up.
• The digest page is read-only. Digest settings are org-level; only owners and admins write them. Ask an admin to change cadence, categories, or recipient rows.
• Preview shows an empty window. No aggregatable events landed in the window — the scheduler skips sending rather than emailing an empty summary.

---