Granular Permissions for Custom Fields
in progress
D
David Fundingsland
I would like to be able to specify which users or teams are allowed to modify any given field.
Log In
Caroline Ginty
Hi everyone! I wanted to provide an update on our development progress on Custom Field Permissions, and also share a design prototype for your feedback. We have been hard at work building out this feature, and making sure that we are adding and enforcing the new permissions checks everywhere in ClickUp where you can use Custom Fields. There are a lot of surface areas to cover, and as with anything regarding permissions, we are taking the time to make sure that it is done correctly to keep your data secure!
Here is a 5 min overview of the functionality and the design prototypes: https://dev-share.clickup.com/clip/s/t333/00706e0d-0586-4e0b-a474-661917a74f6d/screen-recording-2024-02-29-14:30.webm
And here is a link to the Figma prototypes so you can click around yourself - note that not every click is hooked up, but you can always use the arrow keys to navigate through the prototype if you get stuck: https://www.figma.com/proto/q9LB6fdfUMLp7JUGx6e6Cm/CFM-%E2%80%93-Field-level-permissions?page-id=882%3A13955&type=design&node-id=1267-6389&viewport=16122%2C3860%2C1&t=RDMhk50XKj8O0alr-1&scaling=min-zoom&starting-point-node-id=1267%3A6389&show-proto-sidebar=1&mode=design
We would love your feedback on what you see here, the design, interactions, etc so that we can deliver something that will unlock a lot of value for you and your Workspace!
Adam Jaffrey
@Caroline Ginty Any chance you can include this request as part of the granular permissions for Custom Fields updates? It's essentially an extension of what you're working on, but extends the granular permissions to public views as well. https://clickup.canny.io/feature-requests/p/hide-custom-fields-when-sharing-publicly
Ben Valentin
Absolutely need this feature. Odd that it takes so long for base level features like this, Monday.com has had this feature for 5+ years. I prefer ClickUp, but we gotta move a little faster 😅
J
Jose Hernandez
Caroline Ginty - I just watched the video and it looks promising. It would help solve some roadblocks me and my team have. I do have a few questions/feedback.
- all CFs are public to use by everyone across the workspace. So the view only permission doesn't make a lot of sense unless the field has been made private.
- who can give permissions to others to edit and modify a CF? is it everyone in the group who has access to the create and modify CFs, or how is that being handled? I wouldn't want everyone with CF access permissions to start giving edit permissions to others across the workspace as that will create a new set of issues.
- who can make a field private, is it the creator only or everyone with CF management access? how does making a CF private affect the various views? - I'd assume that the users won't be able to see a column on a list unless they have permissions for that CF. How about filtering, how would that work in this case? If there is a field that's being used by multiple users and then you decide to make it private without giving them permissions, do users get notified and would that affect/change their existing work?
- the prototype window does not really work. It just glitches on me. Might try again later, but might want to look at it as users might not be able to test it
Gili Baruch
Hey! I see this massage when trying to change to hierarchy of a specific custom field from "workspace" level to a specific folder. Will the new feature be available to all subscription levels? Here it seems like "Merging & Moving Custom Fields" is already exsist. Was this featurer released?
Lara Worthington
I want to specify which users can delete a value from custom fields. It is far too easy to get it wrong, and there are no warnings given before they are deleted forever, with no ability to restore.
Paulo "ZEH" de Castro
I'm new to the tool and encountered the same issue. It's hard to understand why I can restrict access for Guests but not for Members, for example. This is a critical need since the goal is for a project card to circulate throughout the company, carrying the project's history from the prospecting phase where we sell the project to a client, through to its development, completion, and delivery. Not being able to restrict certain fields so that specific employees cannot access them is essential. Please address this issue urgently!!!
Tim Veles
Looking forward to this important feature!
Caroline Ginty
Caroline Ginty
Load More
→