Notification matrix: per-event in-app toggles in the Profile card #755

Closed
opened 2026-09-25 22:41:37 +00:00 by Cordy · 0 comments
Owner

Round 4 of the #695 deep dive (approved mockup). The reserved "Notifications — coming" card in Account settings → Profile becomes a per-event toggle list. In-app only (mail deliberately not offered).

Semantics: the bell is a derived view, so this is a per-account FILTER, not an event pipeline. Muted events disappear from the bell AND stop counting toward the unread badge; toggling back on resurrects past items inside the retention horizon (nothing is stored per event, nothing is thrown away).

Rows (all default ON, opt-out only):

  • File received from a peer (received)
  • Your transfer was delivered (sent + delivered state)
  • Your transfer failed (sent + failed/refused state) — split from delivered for granularity, failure is actionable
  • Incoming federated share (ocm-share)
  • Your file lock expired (lock-expired)
  • Admin only: licence dropped/restored (license-*, one toggle) — kept mutable because licence health is also exported on /metrics (cairn_license_installed/licensed/seat_cap, #437) for external alerting; default on.

Server: mutedKinds per user in the notify store (rides next to the seen/cleared watermarks — follows the account across devices). GET/PUT /api/v1/notifications/prefs (muted list, validated against the known kind set). Filter applied in feed after the derivation cache, before watermarks/unread count — cache untouched.

Web: matrix card replaces the dashed placeholder in place; toggles save immediately (no Save button); admin row only on admin accounts; i18n ×4. The acctNotifSoon i18n key stays in the dict (qa749 pins it ×4) even though its card is gone.

Round 4 of the #695 deep dive (approved mockup). The reserved "Notifications — coming" card in Account settings → Profile becomes a per-event toggle list. In-app only (mail deliberately not offered). **Semantics:** the bell is a derived view, so this is a per-account FILTER, not an event pipeline. Muted events disappear from the bell AND stop counting toward the unread badge; toggling back on resurrects past items inside the retention horizon (nothing is stored per event, nothing is thrown away). **Rows (all default ON, opt-out only):** - File received from a peer (`received`) - Your transfer was delivered (`sent` + delivered state) - Your transfer failed (`sent` + failed/refused state) — split from delivered for granularity, failure is actionable - Incoming federated share (`ocm-share`) - Your file lock expired (`lock-expired`) - Admin only: licence dropped/restored (`license-*`, one toggle) — kept mutable because licence health is also exported on /metrics (`cairn_license_installed/licensed/seat_cap`, #437) for external alerting; default on. **Server:** `mutedKinds` per user in the notify store (rides next to the seen/cleared watermarks — follows the account across devices). `GET/PUT /api/v1/notifications/prefs` (muted list, validated against the known kind set). Filter applied in `feed` after the derivation cache, before watermarks/unread count — cache untouched. **Web:** matrix card replaces the dashed placeholder in place; toggles save immediately (no Save button); admin row only on admin accounts; i18n ×4. The `acctNotifSoon` i18n key stays in the dict (qa749 pins it ×4) even though its card is gone.
Cordy closed this issue 2026-09-25 23:07:59 +00:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#755
No description provided.