Notification settings should be "default" instead of "none"
Adding existing members to a new project starts all of their notification settings as "none" instead of "default", meaning each person has to manually change the settings on that project.
-
When Leah posted we did not have "change your notification settings click here" link in each email we send. Now we do have it.
For a new project you have 'default', you start getting emails and if your role in this project or your style of work is different - you simply follow any email link "change your notification settings click here" and change it to 'None'. To me this should be both intuitive and logical.
As for suggestion for a project creator to set a default notification level for a project when a project is created - may be. But this will be the same value for all participants.
-
Jai Honeybrook commented
I agree with Leah MacVie that by default, it should definitely be NONE.
Another option could be to have a user setting so each user can choose what their 'default' setting is automatically set to for every new project created (None, Minimal, Full etc)
-
We set 'default' notification level by default :) It means users gets notified on thing they are involved with which is pretty logical. If we set it to 'none' by default as you suggest we will have tons of requests with questions why my team is not getting notified.
What we can do however:
1. Include a link into each email to a page where users can change notifications settings now
2. Let project owners to control their team experience completely. This will require some thought and will take longer to implement. -
Leah MacVie commented
By default, it should definitely be NONE
-
Leah MacVie commented
I CANNOT figure out how to turn off email notifications and my coworkers are ready to KILL me!