# At Field Level

> Part of the NocoDB documentation (Product docs > Granular Permissions). Index of all pages: https://nocodb.com/llms.txt. Any docs page is available as Markdown by adding `.md` to its URL.

URL: https://nocodb.com/docs/product/collaboration/field-permissions
Last updated: 2026-10-03

Field permissions in NocoDB: control who can edit the values of a specific field.

Field permissions in NocoDB control who can edit the values in a specific field of a table. Use them to protect sensitive data, or to make sure that only authorized users can change some information.

## Enabling Field Permissions

To set field permissions for a table:

1. On the field header, open the field context menu.
2. Select **Edit field permissions**.
3. Use the dropdowns to set who can edit the field.

<img alt="Field permissions" src={__img0} placeholder="blur" />

<img alt="Field permissions" src={__img1} placeholder="blur" />

## Permission Levels

You can give a different level of access to each field. These are the options:

| Option             | Who gets access                                                      |
| ------------------ | -------------------------------------------------------------------- |
| **Editors & up**   | Members with **Editor**, **Creator**, or **Owner** roles *(default)* |
| **Creators & up**  | Members with **Creator** or **Owner** roles                          |
| **Specific users** | Selected members or teams                                            |
| **Nobody**         | No one can edit this field                                           |

By default, users with the **Editor** role and higher can edit data in all fields of a table.

| To                                                 | Select             |
| -------------------------------------------------- | ------------------ |
| Stop editors from editing values in this field     | **Creators & up**  |
| Stop all users from editing values in this field   | **Nobody**         |
| Let only selected members or teams edit this field | **Specific users** |

<Callout type="info">
  Only members and teams with 

  **Editor**

  , 

  **Creator**

  , or 

  **Owner**

   roles can be selected for specific access configuration.
</Callout>

<img alt="Field permissions" src={__img2} placeholder="blur" />

### **Additional Notes on Field Permissions**

* Field permissions **do not control field visibility**. Users with access can still see all field data. Field permissions control only who can edit the values in a field.
* Permissions apply at the **field level**, to all records in the table for that field. You cannot set them for one record or for selected records.
* Field permissions are **independent** of table permissions. You can set field permissions without table permissions, and the opposite.
* Field permissions also apply to **API calls** and **shared forms**. Users cannot change field values through these interfaces without permission.
* You can set field permissions for all field types except the types below. These are **calculated or system fields**, and you cannot edit them directly:
  * *Formula*, *Rollup*, *Lookup*, *Created By*, *Last Updated By*, *Created At*, *Last Updated At*, *Button*, *QR Code*, *Barcode*
* For **Link to Another Record (LTAR)** fields, only the permission of the LTAR field in the source table controls editing (adding and removing links). NocoDB does not use the LTAR permissions of the related table.
  * *Example:* **Country** has many **Cities**. A user has permission to edit the LTAR field in the **Country** table. This user can add or remove links to **City** records from the **Country** table. This is true even if the user does not have edit permission for the matching LTAR field in the **City** table.

## Permissions Overview

The permissions overview shows a summary of the current table and field permissions in one table.

To open the permissions overview:

1. Go to the base homepage. To do this, click `Overview` in the sidebar.
2. Click the **Permissions** tab.

<img alt="Permissions overview" src={__img3} placeholder="blur" />

Then select the table that you want to see. The overview shows field permissions and table permissions. You can see who can create or delete records in each table. You can also see which fields are editable, and by whom.

<img alt="Permissions overview" src={__img4} placeholder="blur" />

You can also open `Permissions overview` from the table or field permission configuration modal.

<img alt="Permissions overview" src={__img5} placeholder="blur" />

## Availability

* Field permissions are available on **NocoDB Cloud** (Plus plan and above) and licensed self-hosted deployments (Business plan and above).

---

## Related pages

- [Roles & Permissions](https://nocodb.com/docs/product/collaboration/roles-and-permissions.md): NocoDB roles and permissions at the organization, workspace and base levels, and how NocoDB finds the role that applies.
- [At Table Level](https://nocodb.com/docs/product/collaboration/table-permissions.md): Table permissions in NocoDB: control table visibility, and who can create or delete records in a table.
- [At Dashboard Level](https://nocodb.com/docs/product/collaboration/dashboard-permissions.md): Dashboard permissions in NocoDB: control who can see and who can edit each dashboard.
- [Record Level Security](https://nocodb.com/docs/product/collaboration/record-level-security.md): Record-Level Security in NocoDB uses filter-based policies to control which records each role, team, or user can access in a table.