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 Administration. 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. A scheduled drain delivers withheld digest notices later, one digest for each channel, after the member's chosen digest time in the member's time zone. The drain runs on a recurring schedule, every 15 minutes by default, so a digest can arrive a little after that time. It checks again that the member may see each notice's subject before sending. Choose immediate delivery when you need a notice at once.

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. Changing a delivery choice cannot restore a permission or fix a failed Run. Product configuration remains with Workspace, 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.

Export and delegation

Notifications and settings decide who hears about work and through which channel. Merulan retains each member's preferences, the check on the notice's subject, and the delivery record. Email, SMS, and push delivery run through outside providers behind one channel contract. An exported notice keeps its text and receipts. Reading a copied notice never grants access to its subject or settles the work it names.

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