Skip to content

M5-17 Notification Preferences (Personal + Team)

Milestone: M5 — Disclosure and Verification SOW Reference: FR3 (not explicitly named in the SOW text, but shown in the design wireframe); channel choice ties to the SMS question already raised in M1-01 item 7 Requirement Clarity: 🟡 Found via wireframe cross-check — confirm scope, and specifically whether SMS delivery is really expected (the wireframe shows it as an option, but SMS gateway integration was flagged elsewhere as a spec that quietly disappeared between the original doc and the SOW) Dev Status: ❌ Not started

Overview

The wireframe at docs/design/ui-designs/credential-verification/notification-preferences.html shows a settings page covering: which events trigger a notification (verification completion/failure, batch completion, configuration changes, high-volume alerts), delivery channel (in-app, email, SMS), frequency, quiet hours, and team/role-based notification rules.

Tasks

  • Confirm with Curo whether this level of notification configurability is expected for MVP
  • Confirm whether SMS is genuinely required as a delivery channel (see the related open question on SMS gateway integration)
  • If in scope: build the preferences screen and the underlying notification-dispatch logic per channel

Dependencies

Acceptance Criteria

Not defined in Appendix 3 — needs to be written once scope is confirmed.

Existing Reference Material

  • docs/design/ui-designs/credential-verification/notification-preferences.html

Blockers & Risks

  • Needs decision: same as M5-15/M5-16 — found via wireframe, not SOW text. The SMS question specifically should be resolved alongside the other "dropped spec" items already raised.