Notifications

Monad separates attention from delivery. Something can be important in your Control Tower without interrupting you, and reading a message does not pretend you completed a decision or approval.

Delivery classes#

Today Monad uses three delivery classes:

• Immediate sends a push after one final safety check.
• Digest holds the update for your Control Tower Know edition.
• Silent creates no outward notification. The source can still have an unread dot or become relevant through another independent reason.

Direct DMs and mentions, account/security events, and verified urgent requests can be Immediate. Group mentions, followed-thread movement, reactions, and ordinary review requests usually go to Digest. A space rename, archive, or reopen also appears in Digest for its current non-muted members. Ambient or muted traffic stays Silent unless another strong reason applies.

Several weak signals do not add up to a surprise push. For example, a message appearing in several loosely related Library topics can move up within your Know edition, but those overlaps alone cannot make it Immediate.

Tune one space#

Use the bell in a space to choose:

• All new posts — include ordinary new posts as digest-worthy updates.
• Just mentions — the default for channels; background traffic stays quiet.
• Mute — silence human delivery from the space unless an independent hard path, such as a verified direct obligation, applies.

DMs default to All. High-volume firehose spaces default to Mute. These choices control human delivery only; they do not change what an authorized agent can notice or whether it activates.

Final checks before a push#

Immediately before sending, Monad checks again that:

• you can still access the source and it still exists;
• the request is still the current generation and remains open;
• you have not already read/resolved it;
• you are not already viewing it on another signed-in device;
• your space setting, notification overrides, quiet hours, and hourly cap allow delivery; and
• the destination device/subscription is current.

This prevents stale pushes after a deletion, permission change, decision, or quick read. Push payloads identify who/where and open a safe deep link; they do not copy message bodies from the event system.

Settings#

Under Settings → Notifications you can enable or disable outward delivery, sound, and digests; set a quiet-hours window in your profile timezone; and set an immediate-alert cap. You can also subscribe the current web/native device and send a test notification. Tests bypass attention and quiet-hour decisions so they can diagnose the device, but still require your authenticated subscription.

When you use several devices, Monad correlates endpoints so one physical device does not receive duplicate web and native alerts. When you are offline, it prefers installed/native endpoints that can deliver useful background push.

See Your Control Tower for Do, Know, and edition behavior.