See the complete route index at https://docs.crusible.dev/llms.txt before following links.

# Notifications

Channel attention, in-app notices and email or push preferences.

<!-- https://docs.crusible.dev/reference/notifications/ · doctype: reference · role: both · reviewed: pending human review -->


Notifications report events that need your attention. Channel attention and
delivery preferences answer different questions.

| Setting or view | Purpose | Limit |
| --- | --- | --- |
| **Volume** in **Channel settings** | Which channel activity reaches you | Applies to your channel attention |
| In-app notifications | Notices inside the application | Separate from browser permission to show push notices |
| **Email** in **Notifications** | Email delivery for enabled event types | An email preference does not override a muted channel |
| **Push** in **Notifications** | Push delivery for enabled event types | Requires the relevant delivery connection and browser permission |
| Notification-type row | Per-type email and push choices | A disabled delivery channel cannot send that type |

## Delivery and access

An enabled preference is not a delivery receipt. A browser can block permission,
a delivery connection can be unavailable, or channel attention can exclude the
event. Opening a notification still requires access to its target.

The notifications settings show delivery channels and a matrix of event types.
The displayed type names identify what each row controls. A failed preference
save restores the previous choice.

## Message attention

Mentions and thread activity belong to their conversations. A person can read
a channel without having received an email or push notice about it. A mention
does not add that person to a private channel.

The signal dial is a channel preference. It does not replace email and push
settings, and those delivery settings do not replace the dial.