Notification preferences

Problem Context

• Notifications may arrive through in-app centers, activity feeds, badges, banners, desktop notifications, push notifications, email, chat integrations, digests, sounds, previews, or system-level alerts.
• Users may want different rules for mentions, DMs, reactions, followed threads, watched spaces, assignments, approvals, incidents, security alerts, marketing, reminders, and background jobs.
• Preferences may be global, workspace-specific, organization-specific, project-specific, channel-specific, device-specific, or inherited from admin policy.
• Operating-system notification permissions, mobile overrides, browser permissions, quiet hours, do-not-disturb modes, and email routing can contradict in-app choices.
• A preference that reduces noise can create coordination risk if it suppresses mentions, assigned work, approvals, security warnings, or urgent incidents.

Selection Rules

• Choose notification preferences when the user needs to configure which notification events produce which delivery behavior.
• Use settings management when notification preferences are one category inside a larger persistent app configuration surface.
• Use notification center for delivered-item inbox behavior such as unread state, filtering, retention, mark-read, and related-object cleanup.
• Use follow / subscribe when the user opts into future updates from one object, channel, thread, space, repository, saved view, or topic.
• Use activity feed when users need a catch-up stream of work events rather than delivery rules.
• Use toast notification when the product needs transient current-action feedback that should not require user preference before it appears.
• Use alert, inline message, or banner for current-task blockers that must appear regardless of ordinary notification preferences.
• Use mentions when a sender routes attention; use preferences to control delivery channels for those mention events.
• Expose type-by-channel choices for high-volume products instead of one master on/off switch.
• Show critical exceptions, quiet-hour bypass rules, admin-managed settings, OS permission blocks, and unsaved or failed-save state close to the affected preference.
• Let users preview or summarize what will still notify them before they save aggressive muting or digest changes.

Required States

• Default notification preferences state.
• Per-event-type channel matrix state.
• Immediate, daily digest, weekly digest, and never frequency states.
• Quiet hours or quiet days state.
• Critical exception or bypass state.
• Device override state such as mobile push differs from desktop banners.
• OS or browser permission blocked state.
• Admin-managed or workspace policy override state.
• Muted source, channel, project, or conversation state.
• Keyword or custom routing state.
• Preview privacy or sound appearance state.
• Unsaved changes, saved, failed save, and restored defaults state.

Interaction Contract

• Opening notification preferences shows current saved values for each notification type and delivery channel.
• Changing a preference names the affected event type, channel, device, frequency, and scope before save or immediate apply.
• Quiet hours and digest settings reveal exceptions for urgent, security, assigned, or mentioned work.
• If operating-system, browser, workspace, or admin policy blocks delivery, the affected control explains the owning layer and links to the right place when possible.
• Muting a source or channel does not silently change global notification preferences unless the UI previews that scope.
• Saving preferences confirms what changed and preserves unsaved choices on failure.
• Reset restores only notification preferences or the named group, not unrelated settings.

Implementation Checklist

• Inventory notification event types, sources, urgency levels, delivery channels, devices, default values, critical exceptions, and legal or security requirements.
• Model user preferences separately from per-object subscriptions, delivered notification records, activity feed items, admin policies, and OS permissions.
• Design channel and event-type controls for in-app, email, push, banner, badge, sound, digest, and integration destinations.
• Support quiet hours, quiet days, digest cadence, preview privacy, keyword alerts, custom routing, mobile overrides, and mute behavior where the product offers them.
• Represent admin-managed values, system permission blocks, browser permission prompts, and unavailable channels without pretending the user choice applied.
• Deduplicate deliveries when one event matches multiple subscriptions, mentions, project rules, or digest rules.
• Test keyboard access, screen-reader names, high zoom, mobile layout, long notification type labels, save failures, cross-device sync, policy overrides, and aggressive mute previews.

Common Generated-UI Mistakes

• Offering one master notification switch for a complex collaboration product.
• Letting users disable critical current-task, security, billing, or incident alerts without an exception model.
• Hiding email, push, in-app, banner, sound, badge, and digest settings in unrelated places.
• Showing a preference as enabled when OS permissions or admin policy prevent delivery.
• Using vague labels such as Important, Some, or Recommended without listing included event types.
• Making quiet hours suppress mentions or assignments that the product later treats as urgent.
• Resetting unrelated app settings from a notification preference reset action.
• Failing to deduplicate notifications across mentions, watched objects, subscriptions, and digests.

Critique Questions

• Which exact event types does each preference control?
• Which delivery channels, devices, and frequencies are affected by this change?
• What still breaks through quiet hours, digest, mute, or master-off states?
• Can users tell whether OS permission, browser permission, admin policy, or workspace rules override their choice?
• How does the product prevent duplicate delivery when multiple rules match the same event?
• Can users recover from over-muting before they miss important work?