TLDR: Custom Fields should have a “Viewer” access level
Details: it would be useful to give folks the option to see a custom field, but not be able to edit or change the selection of the field on any tasks. The use case is that we have a portfolio for all new proposals and there is one person who assigns the writer for the proposal, we want everyone on the project to be able to see who the assigned writer is, but not change which writer is assigned.
Hi @Priya_Ghosh1 , this feature is (partially) available on Enterprise plans. However, you will not find it in the modal of your screenshot - those are field members who are able to change the title, description and options of the field itself. What you describe is the ability to not change the values of that field.
Essentially, the User level field member is ‘view only’ since they can use the field but not change its properties - they can change its values on tasks, projects etc. So I would suggest you perhaps rephrase your thread title.
On Enterprise plans, in projects, you can add field restrictions within the project permissions menu, accessed via the project actions dropdown menu, on the right of the project name.
For Portfolios, this feature is not (yet?) available. Your workaround would be to set the portfolio members as Viewers. But that would mean that they cannot change any fields, rather than just the one field you mentioned.
Hope this helps you find an interim solution.
Thanks @Richard_Sather - I’ve updated the title as per your suggestion. You’re right, in my case, either solution would solve my problem, having the additional option for custom fields or expanding the field restriction permission options to Portfolios.
Unfortunately, the workaround you suggested doesn’t work for my case because the project is multihomed to 2 portfolios, so I would want certain fields restricted to the editors in each portfolio. Let me know if you have any other ideas for workarounds, thank you!
