Access roles - custom personal views to be permission managed
I have created a custom role that does not allow the "edit custom public views" and "edit Primary views" - however have noticed that users are still able to toggle the menu and add fields. I know that these will not be there next time the go into the view, but it means that they are selected columns that I want locked down. We have a custom field with selected users which works fine. We have also a space where we tag a particular type of sub project. Having this field available for anyone to toggle means that people are viewing information from other projects that they should be with that field. Is there a way to have an ability in the access roles to not allow changes at all to the views once they are created?
Hi Rhonwyn Williams, thank you for creating this post. When you mention that users "add fields", are you referring to the Table view? Do you mean that users can add columns to the view?
Do I understand correctly that what you'd like to achieve is to restrict users from enabling columns (for example, the custom field you mention) in the Table view?
Or you'd like users not to be able to use certain custom fields?
Hi Juan - Yes referring to the table view where they can add columns to the view
I'd like to restrict them being able to do this in a view that is 'locked down'
I have been hoping for this functionality for a long time. There are instances where we want users to see only what we have set up in the table, but like Rhonwyn mentioned, people can add any field they like. Along these same lines, it would be great if the filtering for views could be locked down as well. So users couldn't add or change views, or use the filters.
Hi Rhonwyn Williams thank you for the clarification, I've passed your feedback on to our Product Team ✅
Russell Sprague, thank you for adding your use case to the thread 👍