Skip to content
Merulan

Notifications and settings

Notifications and settings separate a member's delivery choices and read state from the work that caused a notice.

Notifications and settings keep notices and day-to-day choices in Work & Settings. A notice points to work. A preference changes how a member receives or views it.

Ownership

Notifications belong to the receiving member and keep their own read state. Settings holds member preferences such as theme, time zone, and delivery choices. The Console opens general preferences at /settings/general and notification choices at /settings/notifications. Use the mark-read contract when you need the exact request and result for a notice's read state.

Lifecycle

Notifications keep a stored identity and read state apart from delivery. A member chooses channels for each notice type. An unknown type selects no channel. Push is sent at once when enabled. Daily digest mode holds back eligible email and SMS notices. Withheld digest notices are not delivered later. Choose immediate delivery when you need those notices. No later digest sender completes that path.

Boundaries

Notifications report work. They do not own it. Marking a notice read does not complete a Task or approve a call. Settings owns day-to-day preferences. Workspace identity, membership, policy, and access remain in Governance & Administration. Changing a delivery choice cannot restore a permission or fix a failed Run. Product configuration remains with Installable Products, even when reached through Settings.

Failures

Notifications can fail while their source work remains intact. A review notice failure can leave a visible review Task with task_only coverage. The waiting gate still owns the decision. Disabled channels or daily digest mode can also explain a missing external notice. A preference write failure leaves no confirmed change. Inspect the saved choices before assuming that later notices will use them.

Recovery

Notifications recovery starts at the Task, Run, or approval named by the notice. Check the receiving member's channel and timing choices, save them, then read them back. For a failed review notice, follow Reviews and repair to restore it from the waiting gate. Check the work itself before marking the notice read.

  • Follow Coordinate and recover work when a missing notice has left an assignment unattended.
  • Read Tasks for the state and evidence that a notice cannot replace.