Enable Use of Custom Fields Without Edit Permissions
Alexander Eppstein
Current behavior requires users to have edit Custom Fields permission in order to add an existing Custom Field to a List. This creates a conflict. Granting that permission allows users to modify the field configuration globally, which can affect all Spaces, Folders, and Lists that use the same field.
Requested enhancement.
Introduce a separate permission that allows users to:
• Add an existing, globally managed Custom Field to a List
Without allowing them to:
• Edit the field configuration
• Change dropdown options
This would enable centralized governance of global Custom Fields while allowing operational teams to apply and use them where needed.
This distinction between “use” and “manage” would significantly improve control and scalability for larger Workspaces.
Log In
Caroline Ginty
Thanks for the feedback, Alexander Eppstein. This use definitely makes sense as we think about the next iteration of CF permissions.