Configure Notification Preferences for Pause Status Change Alerts
Coordinators managing large chapters may receive many pause notifications per week and need granular control over notification delivery. The notification-preferences-screen must expose pause-specific notification settings that allow the coordinator to toggle push notifications separately from in-app notifications, set digest mode (immediate vs. daily summary) for voluntary mentor pauses, and always receive immediate push for certification-expiry-driven auto-pauses regardless of digest setting. The notification-preference-service must persist these preferences per coordinator per organisation in the notification-preferences-repository. Preferences must be applied by the pause-notification-orchestrator at dispatch time. WCAG 2.2 AA compliance requires all toggles and labels to meet contrast and touch target requirements.
User Story
Acceptance Criteria
- Given the coordinator opens notification preferences, when they navigate to the pause notifications section, then the notification-preferences-screen shows distinct toggles for: 'Mentor initiates pause', 'Mentor reactivates', 'Certification expiry auto-pause', and 'Reactivation pending acknowledgement'
- Given the coordinator sets 'Mentor initiates pause' to digest mode, when a mentor pauses, then the pause-notification-orchestrator schedules the notification for the next daily digest batch instead of dispatching immediately
- Given the coordinator has enabled digest mode for voluntary pauses, when the daily digest runs, then a single consolidated push notification summarises all voluntary pauses that occurred in the previous 24 hours with mentor names and counts
- Given the coordinator sets 'Certification expiry auto-pause' to immediate regardless of other digest settings, when an auto-pause fires, then the push notification is always dispatched immediately and cannot be batched
- Given the coordinator disables push for a voluntary pause type, when that event fires, then no push is sent but the notification still appears in the in-app notification centre
- Given the coordinator saves their preferences, when the notification-preference-service persists the settings, then those preferences are applied on all subsequent notification dispatches from the pause-notification-orchestrator without requiring an app restart
- Given the preferences screen is rendered, when a screen reader is active, then all toggles have accessible labels that describe both the current state and the effect of changing the toggle, meeting WCAG 2.2 AA criterion 4.1.2
Business Value
Notification fatigue is a well-documented productivity killer in volunteer management contexts. A coordinator overseeing 30+ peer mentors could receive multiple pause notifications per week. Without preference controls, coordinators may disable all notifications wholesale to reduce noise — eliminating the value of the entire notification system. Granular preferences allow each coordinator to tune signal-to-noise ratio while preserving mandatory delivery of high-urgency compliance events, ensuring the notification system remains useful and trusted rather than becoming an annoyance that gets turned off.
Components
- Notification Settings Screen ui
- Push Notification Service infrastructure
- Notification Permission Manager service
- Notification Repository data
- Notification Preferences Repository data
- Pause Notification Orchestrator service
- Notification Preferences Screen ui
- Notification Preference Service service
- Notification Preferences Repository data