Permissions - restrict access to one column

[Lyndon_Penson]

I’m new to airtable, it’s great!

I’m trying to use it for a sign-off / authority database for leave requests, expenses claims etc.

Is it possible to give a collaborator access to some columns but not others on the database? For instance they could create new requests but only people with sign-off authority could tick the “approved” column for requests.

I know you could achieve this effect with a form for new entries but I’d prefer permission controls. Please let me know, thanks

Thanks Lyndon

[Nik_A_Hafiz]

may i know the answer to this if it’s available?

[Katherine_Duh · Accepted solution]

We don’t have this feature right now, but we would certainly consider it alongside other forms of permissioning. If you don’t mind, would you like to tell us a little about why/how you would use this feature? Would using a form instead (as Lyndon suggested above) work for you?

[Nik_A_Hafiz]

hi,

thanks for responding.

my intent is to create a view that still restricts fellow write-enabled collaborators from modifying contents in certain columns whilst able to modify other columns or fields (whether in grid or form view).

example of application for such request would be for certain collaborator(s) like admin at a medical center to update a patient’s visit record but not patients name / id that appear on the same form / grid view.

tks: -nik-

[Colin_Claverie]

I second that.

There is a strong need here for more permissions level, either columns or table. We have sensitive information (i.e. salary) that we’d like to store up in the Air but at the momnet we have complicated workaround.

The idea is to create a table with the salaries and restrict its access to only a few people.

We are using the free version (just because we haven’t reached the limit in place) and would happily pay for these features.

[James_Samuel]

I also look forward to more granular permission control - a must for the reasons Colin offered above. If employees are given editing access to enter data, they end up having access to the entire base which contains sensitive commercial data.

If anyone has figured out a workaround I would be keen to hear it ??

The only thing I can think of is to send records to another base (using the API) and then pulling the completed records back again into the master base.

[Kirk_Nankivell]

Restricting (protecting, locking, whatever we want to call it :slightly_smiling_face: ) editing for columns would be great to ensure that those fields aren’t changed.

It would be incredibly beneficial as I’ve seen others (myself included) accidentally adding new options in a column which creates confusion and a need for constant oversight.

[Toni_Nolasco]

I think love this feature! We are using free version, but with update I will pay sure for using more Airtable. It’s a must have!

[Andrey_Tatarino]

I second this feature. Would be glad to pay to use it.

[James_Rowland]

This is a must have, please implement asap… I’ll pay you.