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! We are getting really close to release for the new Custom Field Permissions functionality and I wanted to share a quick demo and update on where we are with the feature. We're essentially dev complete at this point, just finishing up a few bug fixes and then plan to turn it on internally for ClickUp folks to stress test so we can smooth out any bumps before releasing it more broadly.
Here's a quick demo: https://t333.s.clickup-attachments-stg.com/t333/41c9caaf-27a9-4092-963f-55db57ea5cbe/CF%20Permissions%20Demo.mp4?view=open
A few things to note:
Functionality-wise, I didn't show it very well in the demo, but Custom Fields will support 3 levels of permissions: 1) Edit: can edit field values and also make edits to the field definition (e.g., the options for a dropdown field, for example), 2) Set: can edit field values on tasks, but not make edits to the field definition, and 3) View: can see the field and its values on all tasks and views, but cannot set, update, or delete existing values or edit the field definition. Custom Fields can also be made private, which will hide them from all users except those explicitly given access to the field.
Secondly, along with our other custom permissions features, Custom Field Permissions will be available on the Business Plus and Enterprise plans when released.
Raiyan Asaral
Looking forward to the release!
A
Amit Evlin
So happy to see this progress! it is very much needed♥
you guys are truly awesome!
Laura Reebe
This has more functionality than I anticipated. Great job so far!
Jeremy Gulley
LOVE to see this progress! Amazing work. -- We'd love to beta if you're needing anyone to test.
T
Tom Rüther
Caroline Ginty Hi, that's good progress. What I miss is that you can't set the rights differently in different spaces or lists based on the role. For example:
List 1 = You can view the field
List 2 = You set a value
From my point of view, the system is only filled with duplicate fields and does not lead to a common view.
Robert Hudman
So good!
Caroline Ginty
Hi everyone! We are getting really close to release for the new Custom Field Permissions functionality and I wanted to share a quick demo and update on where we are with the feature. We're essentially dev complete at this point, just finishing up a few bug fixes and then plan to turn it on internally for ClickUp folks to stress test so we can smooth out any bumps before releasing it more broadly.
Here's a quick demo: https://t333.s.clickup-attachments-stg.com/t333/41c9caaf-27a9-4092-963f-55db57ea5cbe/CF%20Permissions%20Demo.mp4?view=open
A few things to note:
Functionality-wise, I didn't show it very well in the demo, but Custom Fields will support 3 levels of permissions: 1) Edit: can edit field values and also make edits to the field definition (e.g., the options for a dropdown field, for example), 2) Set: can edit field values on tasks, but not make edits to the field definition, and 3) View: can see the field and its values on all tasks and views, but cannot set, update, or delete existing values or edit the field definition. Custom Fields can also be made private, which will hide them from all users except those explicitly given access to the field.
Secondly, along with our other custom permissions features, Custom Field Permissions will be available on the Business Plus and Enterprise plans when released.
Valeriya Gosteva
Caroline Ginty super exciting! really looking forward!
Yisroel Falkowitz
Caroline Ginty exciting to the max!! can't wait to use it!!
Joel
Caroline Ginty Waited all this time to find out we'd have to pay double (an extra $1000 a year for us) just to have this simple feature? Well, there goes that.
R
Rebecca Julius
Caroline Ginty this is awesome! How would automations play into this? I have fields now that I want ONLY set by automations - would this new feature allow me to set those fields to never be editable by anyone, but still allow automations to change their values?
Aamir Saleem Sani
Caroline Ginty great thanks for the info, will surely view the demo and let you know about it.
Tim Jasper
David Carn
Caroline Ginty This is great! Your demo showed the list view. This works in the task view as well. Is that correct? Any rough idea on a general release date?
Daniel Urbano
Caroline Ginty this looks great!! Just one question at this point: when a custom field is private, are we going to be able to share it with 'teams' instead of individual members?
Caroline Ginty
David Carn: Custom Field permissions will be enforced everywhere across the app: all views, tasks, dashboards, etc! I'll check back in here with a release date - it's tough to give an exact date right now as it will be dependent on anything that comes up during internal testing on our own Workspace, but I'll update here when we have a better sense!
Caroline Ginty
Daniel Urbano: Yes! Any level of permissions is able to be set for any individual or team, including sharing private fields.
Caroline Ginty
Rebecca Julius: Yes this will be possible!
A
Alex Bowsher
Caroline Ginty LETSSS GOO!! Happy to help test if needed.
Ryan MacAlmon
Caroline Ginty
This is great news! Thank you - when you say "really close to release", are all thinking by the end of Q3 or Q4? Could provide a forward-looking (Safe Harbor) aim?
Will the permissions only by person and teams?, what about by role?
I personally could not get the video to open.
Caroline Ginty
Ryan MacAlmon: Sent you an email! Hopefully the demo will clear up your other questions, but let me know if you have follow-ups. Regarding timeline, I anticipate that this will be released in Q3 and will provide an update once we have a more precise estimate!
David Carn
Caroline GintyBut are we talking this year? Q3?
Caroline Ginty
David Carn Yes definitely. Targeting Q3.
Oleksandr Zalishchuk
Caroline Ginty Will there be an option to hide a custom field from a user or a team?
Caroline Ginty
Oleksandr Zalishchuk: You would need to make the field private and then share it with users and/or teams you'd like to have access.
Umit Gunes
Caroline Ginty I am so excited! Excellent news. I am looking forward to using it!
Courtney Hernandez
Caroline Ginty This is great. Thank you to you and your team for working on this!
Daniel Urbano
Caroline Ginty As follow-up I would suggest adding roles to granular permissions as well.
Mike Mannarino
Caroline Ginty This looks great!! Can't wait to use this feature once it rolls out.
Leslie Surel
Caroline Ginty This is awesome! I'm so looking forward to this. I have two different lists of projects right now, which have a ton of overlap which is inefficient and confusing sometimes. One area all the tasks and to do's which are shared with the full team. A separate list has details like client budget and revenue, which only the owner level should see. With this new functionality for granular custom field permissions, I can finally have everything in one place! I'd be happy to be a beta tester if needed. Thanks to the CU team for your work on this feature.
Ryan MacAlmon
Caroline Ginty - is this idea related?
Caroline Ginty
Ryan MacAlmon: Different feature request! In that one, folks are looking to be able to require a CF in one location and not another; whereas today, if you make a field required, it will be required in all locations.
Ryan MacAlmon
Caroline Ginty Thanks for the quick reply
Daniel Borba
Hi Caroline Ginty , is there an update or estimated release date for the Granular Permissions for Custom Fields feature?
Yisroel Falkowitz
Any updates on this?
Load More
→