SPACES - more granular permissions | Voters

SPACES - more granular permissions

completed

Iann Miller

I would like to be able to assign permissions at the SPACE level.
For example:
TECH SPACE - TechServices Google Group has write access. Principals Google Group has COMMENT access. Cabinet Google Group has READ access.
That way, every newly created project has 99% of the correct permissions going forward as we create them and we don't have to add 20 people to every new Project.

February 7, 2019

Jeff Zeena

Groups? can we add people to groups ?

Ruud

Jeff Zeena: https://help.clickup.com/hc/en-us/articles/6326036524823-Create-user-groups-with-Teams

Ethan Whitted

For those who didn't see, because it wasn't linked, here are the Release Notes announcing this feature add: https://dev-doc.clickup.com/333/d/ad-714989/2023-release-notes/ad-2656373/release-notes-2-196

Louise Ewing

marked this post as

completed

Daniel Urbano

Hi Louise,
Could you please provide details on what has been done at space level for granular permissions? Also, which plans would receive this feature?
Thanks!

Louise Ewing

Daniel Urbano: Hi Daniel, you will now be able to select from full, edit, comment and view-only when you are sharing a Space with a Team or Individual. This new functionality is available on our Enterprise plan.

Ruud

Please be more clear about plans in earlier stages. Recently some logical ones have been pushed to enterprise. I don't see why this isn't relevant for business.

Merging custom fields or moving them to space level was even worse to be honest.

Louise Ewing

Ruud: Thanks so much for your feedback Rudd! I will share this with the team.

Erik @singleton

ENTERPRISE ONLY? I hope you are not serious. This is a SUPER basic sharing functionality. I continue to feel so deeply insulted by this company.

Louise Ewing

Thanks so much for your feedback. I have passed it on to our pricing team.

Ethan Whitted

I meant to comment this much earlier, but I was very disappointed to hear that this feature went only to Enterprise plans and not Business plans. Our company is nowhere near the size needed for a full Enterprise plan yet, but we would definitely benefit from this space sharing permissions feature at our size. I really hope this can be opened up to Business plan users in the future...

Chris McConnell

Is there an update on this or any sort of ETA for rollout?

Louise Ewing

Chris McConnell: We are starting to roll this out!

TRENDUP

very welcome resources. please implement as soon as possible

Louise Ewing

marked this post as

in progress

Hey Everyone! Quick update to share we are currently working on this!

Rob Riccio

Here's how to bring some logic to permissions management with inheritance: 
1st, Allow setting Granular permissions at the Space Level, even the Workspace level.
2nd, If an object is set to 'Public'; share w: [The Parent Level], then it inherits constantly syncing permissions from the parent object.  
e.g. Space: Share w. [Workspace], Folder : Share w. [Space], List: Share w. [Folder], etc. = Inherit & Sync from parent.
3rd, If an object is set to 'Private'; then it does NOT inherit, and you manage the permissions for that object individually by user & permission level.  Changes to parents do not override these object permissions.
You can already manage permissions granularly by setting anything to private and just choosing who can do what.  Then no override by parent permission changes is possible.  So 'public' objects don't need to ALSO
 carry this functionality to protect against undesirable overrides; thus removing the option of INTENTIONAL overrides.
As it exists, there IS NO option for choosing between inherit & sync vs. not; which is really unworkable at the Enterprise level.

Florian Schardt

A feature to manage permissions on a space level would help us to improve the stability of our spaces.
Certain members ("space admins") should be allowed to add/edit custom fields and task statuses (e.g. create a new custom field or create a new status). However they should not be allowed to do so in other spaces.
Currently we sometimes have issues of custom fields disappearing. As there is no history of custom field editing, we do not know who has done the change. We cannot completely revoke the permission to edit custom fields at all, because users should be allowed to handle those in their spaces.

Louise Ewing

Hi Everyone!

While we are still very much looking into more granular Space permissions we have been laser focused on our commitment to quality as our top priority. We will share additional updates on this request as they become available.

Catherine Opina

From a user:
Sure...the idea is a Space is likely one Customer...for example Dr. Scholl's is one of my customers and I run Web Development and SEO for their company but I also have some teams I manage on a project basis for ERP items. Because these are different functions...they have different Folders and different individuals that need to work in those folders. So I would want to be able to make an Admin for say the Web Dev Folder so they can add members and guests as needed to manage the Web Dev work, but then separately add an Admin for the SEO folder who will be adding their own members and guests. Two different functions, two different teams that do not overlap. 
I am an agency so each Space is a customer and each folder is a service...each service has a different manager and team and those managers and teams may not be the same for each Space :) as depending on the platform of the customer...I may use different teams to handle the development.

→