Don't notify users when their level of access to something is changed
Valeriya Gosteva
Every time I "downgrade" someone's permissions (e.g. limit to "view only" to everyone except for a specific group of people who can edit), users get notifications "XXX shared a List/Doc/Task with you".
I have contacted support multiple times about it, and always got a reply that it's a feature not a bug. Which I still disagree with.
I understand that such a notification makes sense when I share something with a person (that they've not had access to), but it becomes detrimental when the same notification is sent when I downgrade the level of their access (to something they didn't know even existed).
Attached is a screenshot of a real email/notification sent literally the entire company got when my colleagues wanted to make their roadmap not editable by other people. As a result, people get confused, the person who changed permissions gets bombarded with messages.
As a result of this notification:
- users are reluctant to make anything public and keep all their workflows private
- users end up ignoring notifications because they get used to the fact some of them are meaningless
- it prevents people from adopting clickup alltogether
I know this sounds minor, but it genuinely is a big problem for us. Therefore, at the very least please change the messaging (i.e. "XXX changed your permissions level from "full" to "view only""), or preferably – remove this notification alltogether.
Happy to chat about it if necessary.
Thanks!
Log In
Louise Ewing
Hi Everyone - Just a quick update to share that we will shortly be making a change to only send notifications when a user is granted access and no further notifications when that access is changed.
Matt Baxter
Louise Ewing thanks Louise. Will we be notified formally when they change is live?
Louise Ewing
Matt Baxter: I will pop back in here and let you know. Probably within the next 3 weeks.
Valeriya Gosteva
Louise Ewing thank you, really great news!
Matt Baxter
Louise Ewing Hi Louise. Just checking in on this. Has this update been rolled out yet? I changed someone’s permission the other day and didn’t get the pop up to say they’d be notified but don’t want to test this en masse until we’ve had confirmation the change is live. Thanks!
Louise Ewing
Matt Baxter: We are still
working on making sure we have this resolved end to end so no public announcement just yet but it's coming :)
M
Michal Marko
Louise Ewing Please, is there an update on when the current setup's issues will be fixed? It's really frustrating.
William Tempel De Donato
Hi Louise Ewing,
Answering your message to Valeriya (that is pinned)
So, please let admins to create a default set for notifications. In our case here we would set "no notifications" as default. The person turns on only the ones are interesting to him.
Why should ClickUp decide which notifications each one will receive or not?
Most of people of the company here receives notifications that they don't want to receive just because it is the default and they did not check the notifications settings from the beginning.
And let be honest... it takes more time to decide which notifications I am turning off or not, then just go there and search for the settings I want to turn on.
W
Wyatt Best
We're not suffering much from this specific issue, but I voted for it because one of ClickUp's biggest weaknesses is the notification volume.
ClickUp is a terrific product, and every little bit helps when it comes to making the notifications better!
Tanner Wixom
I frequently get people reaching out to me when they get this notification after a downgrade in access. It's annoying to have to tell people over and over not to worry about it. What's more, it's just more notification clutter, and I'm already having a hard time getting people to pay attention to their notifications due to the volume of noise in there. We need this change.
Leon Prather
I am not certain that this is how it used to work in 2.0 though... I think we only started hearing from users that they would receive these notifications once we moved to 3.0 beta.
Valeriya Gosteva
Leon Prather: We are still on 2.0 and unfortunately this is definitely how it works for us, and always has
Louise Ewing
Hi James,
Apologies if you didn't pick that up from my response above but addressing little (and big!) tweaks that make incrementally better every single day is our core tenant at ClickUp! I was just shedding some light on the feedback shared from our support team :)
We are constantly working with and engaging with customers like yourself and hearing the feedback first hand so we can quickly implement changes that reduce confusion and create a best in class user experience.
Louise Ewing
Hi Valeriya,
Thank you so much for taking the time to reach out to us again. I'm sorry for the frustration. Our support team are correct in the sense that the product is working as designed so this is not a bug to be fixed. That said as you point out there is room for improvement which would make this a feature request! I'm a PM here at ClickUp and this is within my area of scope and agree with a lot of what you shared. We are making a lot of incremental changes to how permissions work this year and feedback like this helps us really fine tune our user experience. This is now on our radar!
James Hogg
Louise Ewing: https://www.wired.com/story/its-not-a-bug-its-a-feature/
Maybe you need a new lexicon. A feature request should be something new or requested behaviour change to enhance product. What is being asked for is a feature repair to fix an implementation that is faulty. It should not go into the same basket as a feature request. As Val indicates having a lazy alert that is generic every time permissions change is confusing users. Things that confuse users should be at top of your list to fix as getting user adoption of new platforms is hard and ClickUp is making that harder seems to be ignoring the little tweaks to make your app logical and user friendly.