[Notifications] Notification Preference Granularity #12

Closed
opened 2026-06-23 00:42:35 +00:00 by rbrooks · 1 comment
Owner

Give users a clearer way to decide what they receive as notification surfaces multiply (reminders, recap emails, weekly digests, Discord bot events, campaign-level controls).

Scope

  • Add a more explicit per-user notification preferences model.
  • Let users control categories: reminder emails, recap emails, weekly digests, and optional bot-driven nudges where applicable.
  • Make campaign-level and user-level settings compose predictably.
  • Surface the effective notification behavior clearly on the Profile page.

Design rule

  • Campaign settings enable a capability; user settings opt that user in or out of receiving it.
  • Keep the UX simple - avoid a matrix of confusing toggles.

Roadmap: Platform and Delivery ? Notification Preference Granularity (P4).

Give users a clearer way to decide what they receive as notification surfaces multiply (reminders, recap emails, weekly digests, Discord bot events, campaign-level controls). ## Scope - Add a more explicit **per-user notification preferences model**. - Let users control categories: reminder emails, recap emails, weekly digests, and optional bot-driven nudges where applicable. - Make campaign-level and user-level settings **compose predictably**. - Surface the effective notification behavior clearly on the Profile page. ## Design rule - Campaign settings **enable a capability**; user settings **opt that user in or out** of receiving it. - Keep the UX simple - avoid a matrix of confusing toggles. _Roadmap: Platform and Delivery ? Notification Preference Granularity (P4)._
Collaborator

Folded into #655 (owner decision, 2026-09-15). The preferences model this issue asks for is now the settings half of #655. #655 adds an in-app bell with a notification history, and delivery settings for each person across email, Discord DMs through the bot, and browser push later. It keeps this issue's design rule: campaign settings enable a capability, personal settings opt in or out, and no matrix of confusing toggles. It also keeps the requirement to show each person's effective settings on Profile. #655 moves to v4.6.0 because Discussions (#654) depend on it. Closing this issue in favour of #655.

**Folded into #655 (owner decision, 2026-09-15).** The preferences model this issue asks for is now the settings half of #655. #655 adds an in-app bell with a notification history, and delivery settings for each person across email, Discord DMs through the bot, and browser push later. It keeps this issue's design rule: campaign settings enable a capability, personal settings opt in or out, and no matrix of confusing toggles. It also keeps the requirement to show each person's effective settings on Profile. #655 moves to v4.6.0 because Discussions (#654) depend on it. Closing this issue in favour of #655.
Sign in to join this conversation.
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
rbrooks/Quest-Board#12
No description provided.