Preferences & quiet hours
Beyond who receives a given event type by default, every user decides how they want to receive it themself — which channels to use, when they don't want to be disturbed, and whether they'd rather get a batched summary instead of individual messages. These settings are personal — they don't require administrative permissions.
Who it's for
Every signed-in user manages their own preferences and their own quiet-hours window — there's no role split here. Both are kept per organization: if you belong to more than one, switching the active organization in the console switches which copy of your quiet hours you're editing. That sets these settings apart from alert rules, which override who receives a given event type at all, and do require administrative permissions.
Key concepts
The in-app record is always created regardless of your other settings — it's the canonical entry you see in the notification center. Email, SMS and push are external channels: you can turn each one on or off independently, per event type. SMS is always delivered immediately — there's no digest mode for that channel.
Channels and delivery mode
For every event type you set, separately, whether you want email, SMS and push; an absent preference means the channel is on by default. For email you additionally choose a delivery mode: immediate, daily digest, or weekly digest — described below in the Digests section.
Quiet hours
Quiet hours are a single daily window (it may cross midnight), set in your own time zone, during which push and SMS notifications are held instead of delivered right away — the in-app record is always written without delay, regardless of the window. Held notifications are never lost: the platform delivers them automatically as soon as the quiet-hours window ends, so they simply wait until morning (or whatever time you set), never disappear. By default, critical-severity events (e.g. an active hours-of-service breach) bypass quiet hours and land immediately — you can turn that behavior off if you'd rather nothing at all interrupt your quiet window.
Digests
Instead of getting a separate message for every event, you can switch the email channel to a daily or weekly mode for the event types you choose — every notification held over that period is then batched into one summary email. The same mechanism applies to the non-email channels (push and the in-app record): instead of many individual entries in the notification center, one aggregate summary appears in their place.
In the background
The daily email digest and the non-mail digest (push/in-app) go out every morning; the weekly digest goes out once a week, Monday morning. A separate, frequent job checks every few minutes whether a user's quiet-hours window has ended, and delivers their held push/SMS notifications without further delay.