Propose new features
Designing Decidim together
Add granularity to notifications
Is your feature request related to a problem? Please describe.
Admins and users can receive a lot of unwanted notifications, but can't be precise about what they want or do not want to receive. If they think they receive too much notifications, their only option is to disable completly the mails in notifications settings.
But sometimes, a user following a participatory space juste want to receive a notification when a new proposal is made, not for each comment posted.
Describe the solution you'd like
As a user, I'd like to be able to select the type of contents submited to notifications, in my notifications settings.
Describe alternatives you've considered
Does this issue could impact on users private data? Ex. issues related with user's sign up/sign in process, verifications, invitations, sensitive data like email, IP addresses, etc.
This proposal has been accepted because:
- Reviewed by @product and accepted in the main project
- Funded by Barcelona City Council
- Developed by Populate
- Available in release 0.27 via #8833
List of Endorsements
Report inappropriate content
Is this content inappropriate?
You are seeing a single comment
View all comments
Conversation with Simonas Zilinskas
Hey @carol ! Replying to the comment two years later, granularity implies for the user to be able to choose whether they are informed (separately) about:
- new proposals
- new comments
- new endorsements
- updates to comments
Our instances have a few edge cases where a user updates a comment 20 times per day, so even in the digest this would be overwhelming. We thus suggest to add more granularity.
We are currently looking into some data and best practices on the topic :) Will keep you updated
The grouping of notifications is great though!!!
Hi @simonas, I agree and I'm afraid that those edge cases are actually not so edgy 😬 (here at Metadecidim we already experienced the countless edits to a comment). So any improvement in that direction is welcome!
In fact, it would be great to have a map of all the current notifications, and who receives them. I mention it because I remember a cool spreadsheet from someone at OSP where you had started mapping by role and component. Maybe @Pops remembers it? But watch out for the rabbit hole, with @NilHB and @andres we were just talking about how Slacks handles this 😅 https://twitter.com/vponamariov/status/1582671678328344576/photo/1
Indeed I remember this spreadsheet, we had spent 3 months making it with @Antoine on the 0.21 version in 2020 😂 This would be a veryyy cool thing to do again for the 0.28 version for example, but it's time consuming...
We could put together a team in the community to do one again, I'm in!
And we could start from the old spreadsheet of course
It would be cool, if we put together a good Notifications Squad 🔔 it shouldn't be that painful. Maybe at the beginning of next year we could do a couple of sessions and see how it goes?
I love the idea!
Loading comments ...