Open agjohnson opened 1 year ago
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.
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.
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:
Front conversations