Advanced Permissions/Permissions per user
building now
J
Justin Hayes
Hello! I'm a system administrator for a company with 120 employees, and I'm hoping to make a feature request. I would really appreciate it if we could have more control over custom permissions for each individual, and the ability to create permissions based on more options. Specifically, I'd like to set permissions for things like creating or copying a list, moving tasks to certain statuses, and restricting access to creating or updating labels. Basically, I want complete control over what each person can create or edit. For example, I'd like to restrict certain people from editing specific custom fields.
Currently, the role system is limited, and some members have the same permissions as others, which isn't ideal. Many of my supervisors are members, but I don't want them all to have access to everything. While there are different roles we can create, the options for setting permissions are very limited. It would be great if we could have more flexibility in creating custom permissions for each individual.
Log In
Armine Seropyan
Hey everyone!
We are working on the change that would help to define exactly what users can and can't do on different hierarchy locations, going beyond the standard pre-defined Full, Edit, Comment, and View Only levels.
You'll be able to create permission sets that combine specific actions like creating tasks, managing statuses, editing custom fields, tracking time, and assign it to teams or users.
Open to chat more about this change — appreciate everyone's feedback here! 🙏
Amy Rudy
It would be great to be able to lock things down by task type too. So only certain people can edit fields for a task type while others could just view. Really hoping to be able to lock things down more.
S
Sean Louden
Why does the Business plan not allow granular permissions?
I upgraded from Free to Unlimited specifically because I was led to believe I would be able to control user permissions. Now I’m being told that this basic functionality requires another upgrade.
That is a blatant bait-and-switch. Permission controls are a fundamental business feature, and ClickUp’s pricing and upgrade flow should make these restrictions clear before customers pay—not after.
Gigi Garcia
This sounds fantastic. I’d also love to see a layered permissions model that allows system administrators to delegate certain permission-management capabilities to users in roles like Champion. For example, a system admin could grant Champions the ability to enable or disable specific permissions at the folder or list level for members within their space.
One practical use case is list exports. Currently, exporting appears to be disabled for Members globally, but there are situations where Members may need export access for specific lists or folders they own or manage. It would be valuable to have the flexibility to control permissions like exporting at a more granular level, rather than applying them across the entire workspace.
J
Joseph Plaizier
Does this new feature by chance also include permissions for ability to archive? We have some users who archive when they shouldn't be.
Marcelo Goebel Machado
Armine Seropyan any expected date for the release of this feature?
Wendy Mencsik
Would love to see a view only capability for user role and role permissions. Due to our company's strict security process, our in-house CU super users/SMEs are not authorized to edit or create roles nor are we able to assign a role to a user. B/c of the way CU is built, this means we can't even see what permissions are in a role or what role a user is assigned. This makes it incredibly difficult to troubleshoot when we suspect the issue someone is experiencing is related to their permission rather than a bug or user error.
Philip Lucas
Excellent! Could we please also make it so that Admin and Owner (or at least one of them) can access ALL Spaces/Folders/Lists in a workspace even if they are marked private?
Brenno Vicario Nicolau
At the moment, enabling Protect View prevents users from saving changes to a view; however, it still allows temporary modifications during their session (such as adjusting filters, sorting, grouping, or columns). While these changes are not persisted, they can still lead to inconsistencies in how information is displayed and interpreted across the team.
For certain operational and standardized workflows, it is essential that specific views remain completely immutable—not only in terms of saving changes, but also in preventing any form of temporary modification.
Introduce an option within Protect View that enforces full immutability, ensuring that:
1) Users cannot modify filters, sorting, grouping, or visible fields
2) The view remains exactly as configured for all users at all times
3) Any attempt to change the view is restricted or disabled
This would be especially valuable for teams that rely on consistent, standardized views for reporting, auditing, or operational control.
Michał Mrzygłocki
Delete custom field should be only for admins and owners
Steve Lee
It would be great if we can manage the permission to change the task status by user level, especially for guest users. For an instance, I would like to prevent the guest users changing the task status.
Load More
→