Omniscio

PM Notification Preferences

Per-board notification preferences for Mission Control: each board can be muted, promoted, configured for email delivery and given a digest frequency, with session-scoped batching, a never-notify-actor filter, and preferences stored locally and synced over the PM push channel.

On this page

What it is

Status: shipped. Part of the Mission Control PM system (requires missionControlEnabled).

Per-board notification preferences for Mission Control. Each board can be muted, promoted, configured for email delivery, and given a digest frequency.

Where to find it

Preferences are set per board, one board at a time. The same preferences — plus the recent PM notification events, the notification feed and marking a notification read — are reachable over the CLI routes listed under For agents, which is how to reach them when no board is open on screen.

How it behaves

Users set preferences per board via five controls (the PmNotificationPreference fields):

  • muted -- suppress all notifications from a board. This is the ONE per-board mute list: the board rows, change batches and due alerts all honour it, and boards set to "None" in the old Settings dropdowns were moved here.
  • promoted -- elevate a board's notifications to higher visibility.
  • emailMode -- email delivery mode (off / instant / digest).
  • digestFrequency -- digest cadence (daily / weekly).
  • mutedEventTypes -- selectively silence specific event types (e.g. item_status_changed, comment_added, dependencies_resolved) while keeping the rest. Stored as a JSON string array; when a board is fully muted the per-event controls are hidden because they have no effect. A save that leaves the field out keeps the stored list; send an empty array to clear it.

Notifications use session-scoped batching with per-board mute/promote routing and a never-notify-actor filter -- the person who performed an action is never notified about their own change. Preferences are stored locally and synced via the PM push channel (PM_NOTIFICATIONS_UPDATED).

What a board that is not muted sends is decided by the Inbox level in Mission Control → Settings → Updates (Everything / Involves me / Mentions me / Nothing) — see mission-control-part-4.md. A board can also carry an internal cap at Involves me (inbox_level), set when an old "Assigned to me only" choice was carried over. A muted board, or one capped at Nothing, also keeps its automations' "failing repeatedly" alert out of the Inbox.

Notification preferences belong to the Mission Control PM system, so mission-control.md is the parent page. The Ops Engine dashboard renders a per-board notification preferences panel of its own, and is documented in pm-operations-engine.md.

Last verified 2026-10-06