With field and table editing permissions, you can limit who can make certain changes to a field or table. For example, you can make sure that only some coworkers can mark a project as approved, or prevent anyone from inadvertently deleting records.

What you'll need 

To configure field and table editing permissions, you’ll need creator or owner permissions to a base within a Pro or Enterprise workspace. To confirm your permission level, open the base and click Share in the top right. If you don’t have creator or owner permissions, ask someone with creator or owner permissions to grant you this access.

Getting started

Limit who can change the contents of a field

Anyone with creator or owner permissions can limit who can edit the contents of a specific field, such as checking a checkbox or typing in a text field.

1. Click the dropdown next to the field’s name > Edit field permissions
2. Select who you would like to be able to change the contents of a field. You can select permission levels (Creators and up, Editors and up, Nobody), or specific users.
3. You can also determine whether the field can be filled out on forms.
1. If Allow this field to be set in records created through forms is off, the field will be grayed-out on any forms it has been added to. Ensure the field is not required on any forms, or people will not be able to submit those forms.
2. If Allow this field to be set in records created through forms is on, the field will be able to be filled out on forms.

When someone who does not have permission to edit the field clicks on it, a lock icon will appear. Other actions that would edit the field will also be disabled, such as:

• dragging the record in a calendar, kanban, or grouped records view
• cutting from or pasting into the field in a grid view

Limit who can create or delete records in a table

Anyone with creator or owner permissions on a base can limit who can create or delete records in a table.

1. Click the dropdown next to the table’s name > Edit table permissions
2. Select who you would like to be able to create records, and who you would like to be able to delete records. You can select permission levels (Creators and up, Editors and up, Nobody), or specific users.
3. You can also determine whether records can be created through forms.
1. If Allow records to be created through forms is off, any forms associated with the table will stop accepting submissions.
2. If Allow records to be created through forms is on, forms will continue to accept submissions.

People who are unable to create records will see the options to create records grayed-out, with an explanation that the table is locked. Other actions that would create records will also be disabled, such as:

• duplicating a record
• inserting a record at a particular spot
• creating a record in other views
• creating a record from a linked record field

People who are unable to delete records will see the option to delete records grayed-out.

FAQ

Who can change or remove the restrictions that I’ve set?
Anyone with creator or owner permissions on the base can configure or remove field/table editing permissions.

Why am I not seeing “Edit field permissions” or “Edit table permissions”?
You’ll need creator or owner permissions to the base or workspace. To confirm your permission level, click Share in the top right of the base. If you don’t have creator or owner permissions, you’ll need to ask someone with creator or owner permissions to grant you this access.

How can I adjust who can see information in my base?
Field/table editing permissions do not affect who is able to see information in the base. To share only a limited subset of information in your base, use a view share link and optionally, a form.

Is it possible to lock a field’s configuration?
At the moment, field locking doesn't include locking a field's configuration (name, type, single select options). If this would be helpful to you, we'd love to hear more about your use case at support@airtable.com.

Where do field and table editing permissions apply?
Anywhere that edits can be made - field and table editing permissions apply to our mobile apps, blocks, and to edits made using the Airtable API.

Can I limit editing to just an API script or integration?
Yes, if you limit editing to the specific user whose API key is used by the API script or integration.

Learn more

• Prevent others from editing a view’s configuration with locked views
• Share part of a base with a view share link
• Allow people to add records without needing access to the base with forms