We are running into challenges in having a large number of users with Editor permissions that need to be able to update records in our tables, but also make changes to the View configuration (filters, groupings, etc) that break usage models that we’ve put in place.
The bulk of our users are ones that need read-write permissions at the record level, but don’t need the ability to change the view filters/configuration of public, shared views. So our use case is something like this:
- Configure a views that work well for a given purpose
- Assign an owner responsible for making any changes to the view configuration (including fielding requests for such changes). For example, a “View Owner” field at the View level.
- Lock this configuration, such that it can only be unlocked and edited/updated by the above owner
- Make the view visible to all our users as a sort of “officially blessed” view
- Allow other users to edit the records but not change the view configuration in-place
- Allow them to clone the view privately if they want to make their own version of the view (but leave the original untouched), for example via Private Views
- Make sure everyone can determine who the “owner” user is so they can contact them to ask for changes / updates to the locked view.
Private views don’t do it because their visibility is tied to all users, not individual views – we want to be able to show/hide (or publish/unpublish) one view at a time, vs show/hide everyone’s private view.
I’m aware that user permissions is an active area of enhancement requests, so this overlaps somewhat with the following (especially the first two), but I couldn’t find this specific use case written up so I thought I’d submit it independently.
- Limiting Editor Permissions
- 'Locked' view filters
- Private or User Views and Reverting to Sticky Public Views
- Airtable-Based Art Portfolio Web Site