# At Table 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/table-permissions
Last updated: 2026-10-03

Table permissions in NocoDB: control table visibility, and who can create or delete records in a table.

Table permissions in NocoDB control **what users can see** and **what actions they can perform** in a table. Visibility sets if a table exists for a user. Record permissions set who can create or delete records in that table.

## Table Visibility

Table Visibility sets if a user can find and open a table and its views in a base. When a table is visible, the user can use it as their roles and permissions allow. When a table is not visible, NocoDB treats it as not there for that user.

<Callout type="note">
  Only 

  **Base Owners**

   can configure table visibility settings.
</Callout>

These are the visibility options:

| Option                      | Who can see the table                                    |
| --------------------------- | -------------------------------------------------------- |
| **Creators & up**           | Members with **Creator** or **Owner** roles              |
| **Editors & up**            | Members with **Editor**, **Creator**, or **Owner** roles |
| **Specific users or teams** | Only selected members or teams                           |
| **Everyone**                | All members of the base *(default)*                      |

<Callout type="note">
  Note:

  * By default, all tables are visible to everyone in the base.
  * Table visibility is evaluated before checking record permissions. If a table is not visible to a user, they cannot access it or perform any actions within it, regardless of their record permissions.
  * Hidden tables will be excluded from APIs, Automations, Scripts & Extensions that list or access tables.
</Callout>

### Configuring Visibility

To configure the visibility of a specific table:

1. In the sidebar, click the `⋯` icon next to the table name.
2. Select **Edit table permissions**.
3. Use the dropdown menu next to **Who can see this table?** to set the visibility.
4. If you select **Specific users or teams**, select the members or teams that can access the table.

<img alt="Table visibility" src={__img0} placeholder="blur" />

<img alt="Table visibility" src={__img1} placeholder="blur" />

<img alt="Table visibility" src={__img2} placeholder="blur" />

Only Base Owners can change table visibility settings. Other members do not see this option in the menu.

### Visibility Notes

**Shared bases and shared views**
Table visibility applies to shared access. In a shared base or shared view, you can access only the tables with the visibility option **Everyone**.

**Relational fields**
When a table is hidden from a user, relational fields that link to that table show only the **display values** of the linked records. If the role of the user allows it (Editor+), the user can still link or unlink records from the source table. But the user cannot open or access the linked records. Lookup and Rollup fields continue to work and show values from the hidden table. They do not give visibility of, or access to, that table.

For a relational field that links to a hidden table, the edit modal shows the table name as "Private Table" and the view name as "Private View".

<img alt="Relational field visibility" src={__img3} placeholder="blur" />

**Duplicating bases**
When a user duplicates a base, NocoDB copies only the tables that this user can see. The new base does not include tables that are hidden from that user. Thus, the new base also does not include relational fields that link to hidden tables. Formula fields that refer to these relational fields can show errors because the references are missing.

## Table Record Permissions

Table Record Permissions set the actions that a user can do on the records in a table. When you give permission, users can create or delete records as their roles and access levels allow. When you restrict permission, those actions are disabled. The table and its records can still be visible to the user.

### Configuring Record Permissions

To set record permissions for a table:

1. In the sidebar, click the `⋯` icon next to the table name.
2. Select **Edit table permissions**.
3. Use the dropdown menus to set who can:
   * Create records
   * Delete records

<img alt="Table permissions" src={__img4} placeholder="blur" />

<img alt="Table permissions" src={__img5} placeholder="blur" />

#### Permission Levels

You can give a different access level to each action (create record or delete record). 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 or teams** | Selected members or teams                                            |
| **Nobody**                  | No one can perform this action                                       |

By default, members with the **Editor** role and higher can create and delete records in a table.

| To                                               | Select                      |
| ------------------------------------------------ | --------------------------- |
| Let only creators and owners do the action       | **Creators & up**           |
| Stop all record creation or deletion             | **Nobody**                  |
| Let only selected members or teams do the action | **Specific users or teams** |

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

  **Editor**

  , 

  **Creator**

  , or 

  **Owner**

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

<img alt="Table permissions" src={__img6} placeholder="blur" />

### Record Permission Notes

* Table permissions **do not control record visibility**. Users with access can still see all records. Table permissions control only who can create or delete records.
* Permissions apply at the **table level**, to all records in the table. You cannot set them for one record or for a subset of records.
* Table permissions are **independent** of field permissions. You can set each one separately.
* Table permissions also apply to:
  * Record creation or deletion through **APIs**
  * Record creation through **shared forms**

## Permissions Overview

The permissions overview shows a summary of all table and field permissions in the base.

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={__img7} placeholder="blur" />

Select the table that you want to examine. The overview shows table permissions and field permissions. It shows who can see the table, who can create records and who can delete records. It also shows the visibility of each field in that table.

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

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

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

## Availability

* Table Record Permissions are available on **NocoDB Cloud** (Plus plan and above) and licensed self-hosted deployments (Business plan and above). Table Visibility is available on **NocoDB Cloud** (Business plan and above) and self-hosted Scale and Enterprise plans.

---

## 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 Field Level](https://nocodb.com/docs/product/collaboration/field-permissions.md): Field permissions in NocoDB: control who can edit the values of a specific field.
- [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.