Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add user preference dashboard for notifications #10882

Open
1 of 3 tasks
agjohnson opened this issue Nov 1, 2023 · 2 comments
Open
1 of 3 tasks

Add user preference dashboard for notifications #10882

agjohnson opened this issue Nov 1, 2023 · 2 comments
Labels
Feature New feature Needed: design decision A core team decision is required

Comments

@agjohnson
Copy link
Contributor

agjohnson commented Nov 1, 2023

We started to add some user preferences for notifications recently, but we also talked about moving these to a dedicated UI page and expanding some of the options users have on that page.

Currently, there are a few deprecation specific notification options on the main profile page form. These can actually be removed as the deprecation has passed. These options are specific to single notifications.

What we may be aiming for is instead of giving the user opt out for a single notification, we want to make the opt in/out more generalized, so users can opt out of more notifications and/or future notifications.

We haven't dug too deep into what we want exactly here, but a few ideas were:

  • Use Sendgrid to manage opt-out? I believe there are some native features that help us here. We might need to use internal modeling either way though.
  • Standard email opt out options might be the best pattern, which would be to give the user message classes to opt out from -- "marketing", "suggestions", "notices", etc.

  • Drop existing notification preferences, they aren't use anymore afaik
  • Add some layer for opt out modeling -- continue using internal modeling or use Sendgrid for opt out
  • Add UI for opt in/out -- form, view, etc in user preferences dashboard

Front logo Front conversations

@agjohnson agjohnson added Feature New feature Needed: design decision A core team decision is required labels Nov 1, 2023
@humitos
Copy link
Member

humitos commented Nov 6, 2023

This is out of the scope of the new notification design document I'm working on at #10890, but if we go in that direction and implement it, we can easily add a new field to the Notification model to track this and decide whether or not show/list/send notification based on user's preferences.

# Group defined for opt-out via notification preferences
group = models.CharField(choides=[MARKETING, SUGGESTIONS, NOTICES])

This issue is more related to email notification in my opinion, where the new notification system is more based on site notifications. We can eventually adapt the new notification system and use it for emails as well, but I don't want to start that big and focus on our main goal for now.

@agjohnson
Copy link
Contributor Author

This issue is more related to email notification in my opinion

Yup, this is exclusively for email notifications I feel. I don't think we need on site notifications to be configurable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature Needed: design decision A core team decision is required
Projects
Status: Planned
Development

No branches or pull requests

2 participants