Protect View (New Members) Persist Bulk Settings
Innocent Buthelezi
When protecting a view, and selecting the bulk options to protect for all members, that setting is not persisted for new members. Meaning you have to go through every view that's protected and select the setting for any newly added member
Log In
K
Koen Vanneste
Additional information :
After adding a new member to the space, folder, list, … whatever, this user – assigned to the standard member role – automatically has EDIT rights so he/she can UNPROTECT each view in the location they are assigned to.
In my case, a new employee arrives in my DEV team. I invite this user to ClickUp (No Microsoft SSO in the Business Plus plan : Please change this policy, because now only part of the enterprise plan !) as a member. Consecutively I share a couple of spaces with this new user. As such, this (member) user has now rights to do everything according to the member role.
Unfortunately, there is no setting in the ‘security & permissions’ screen to restrict members from unprotecting views made and protected by an admin, without removing the right to also create views. As such, as an admin, I have to edit the permissions of each view on each hierarchy level (these are hundreds of views) to properly set the permission for this new user to ‘can’t unprotect and protect’ !
K
Koen Vanneste
Clickup support asked me to put this on the feature request board as well. I was glad to see that this topic is already here !
Clickup support wrote :
"
In regards to wanting the ability to have new members not be able to unprotect views unless you specify and to limit this ability separately from preventing members from editing views, at the moment, that is not available in ClickUp. Though it's worth exploring!
"
Like James Reed was telling :
I have 17 list-views for every new tasklist. 15 members x 17 views x 100 tasklists = 25500 clicks !
Please note that since one of the latest updates, the bulk option to protect for all members has gone ! Please put this back !
Also note that, when you unprotect a view, change what you need to change, and then protect the view again, you need to go through the protection permissions for every user AGAIN. Previously, unprotecting a view would not unset the current view permissions. So when protecting the same view again, all individual permissions for every user were still there, and by simply protecting the view again without changing each individual permission, the view was protected with 1 click.
Now, since one of the latest updates, this is not the case anymore ! Please fix this, as we all lose precious time !
C
ClickOps Dashboard Centre
100 clients x 6 Views each x 40 (20 users who have to be checked for protect and unprotect) = 24,000 clicks.
Much less clicks to just write the code that allows us to set in globally.......
J
Jacob Tankersley
I was directed here by ClickUp's Customer Support. Documentation claims Members and Guests will default to "Cannot protect and unprotect view" but that is not the case. I assume that was the intent but somewhere the default setting was not adjusted. This function is CRUCIAL to the overall value of the Business Plan. The Protect View feature is a GAME CHANGER, assuming it has the proper defaults. Currently it is a hassle to go edit permissions for protected views. Sharing folders/lists/views to Teams, instead of individual members, and editing permissions at that level would be a decent work around. However, Team Sharing is not available except in the Business Plus and Enterprise Plans, thus the Protect View feature is of no value in the Business Plan. Unfortunately we have no incentive to upgrade to the Business Plan as this feature presents the most value. And jumping to Business Plus requires addition of features we simply do not need yet.
Benjamin
Zeb This is insane, how can ClickUp have ever thought that this is a good idea.
Nick Potok
Hey Benjamin, Nick here, hopping in for Zeb. We completely understand your sentiment and appreciate the strong nudge. I have escalated this issue with our development team and we will work to address it straight away. Thank for your patience while we find a resolution.
Benjamin
Nick Potok: Thanks for picking this up Nick.
K
Koen Vanneste
Nick Potok: Any resolution yet ? Because since one of the latest updates, this functionality has become even worse.