This Product Ideas board is currently undergoing updates, but please continue to submit your ideas.

Limiting Editor Permissions

Showing results for 
Search instead for 
Did you mean: 
5 - Automation Enthusiast
5 - Automation Enthusiast

Hi, having lots of issues where Editors are continuously hiding or re-arranging fields on a shared grid view. It would be great if user permissions to hide and remove fields was limited to Creators. Also +1 for more granular user permissions in general. Thanks!

4 - Data Explorer
4 - Data Explorer


It would make Airtable SO, SO much more user-friendly to have another permission level below ‘editor’, which could add and modify existing records, but NOT delete them, nor make changes to sheets or views.

Call it ‘contributor’ or ‘updater’ or ‘inputter’ or something like that.

It seems crazy that there is such a large permission gap between the current ‘editor’ and ‘commenter’ functions. Currently we have to work around this by giving very explicit training to the people who are inputting data for us along the lines of “PLEASE PLEASE DON’T TOUCH THIS OR YOU’LL BREAK EVERYTHING”. Would be so much easier, less anxiety for them and us, if we could just remove that ability to delete things.

To be clear about how much this is wanted - my org is currently on the free plan but if you had this in the Premium set, we would DEFINITELY pay for it.

I would be so happy to be part of a feature consultation group to get this designed and shipped ASAP.

(A further extension and different feature request would be the ability to lock certain columns from being edited by people with ‘inputter’ access levels and below.)

4 - Data Explorer
4 - Data Explorer

Agreed. I’m on the pro plan 14 day trial, and I’m not sure that I can make this work without the ability to offer access more limited than editor, but less limited than commenter.

Ideally there would be an access level that could not create/delete any views, but could edit the data within the views of their permission.

Also, would be helpful to be able to “lock” fields from the hypothetical new permission level.

4 - Data Explorer
4 - Data Explorer
  • 1 for this feature: updater/inputter
6 - Interface Innovator
6 - Interface Innovator

Also HUGELY agree that there should be a middle ground between Editor and Commenter - this would be great because you could fix the views they could see and then they couldn’t add or change the views you allow them to see, which would protect sensitive information.

10 - Mercury
10 - Mercury

We made a tool that allows you to share a view with people who need limited access only.