# Base Collaboration

> Part of the NocoDB documentation (Product docs > Bases). 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/bases/base-collaboration
Last updated: 2026-09-27

This article explains how to invite members or teams to your base, manage their roles, and remove them when needed.

## Invite Members to Base

1. Open the base and go to **Base Settings** → **Invite** → **Members**.
2. Click **Add Members**.
3. Click the field under **Invite specific people**.
4. Enter one or more email addresses, comma or space separated.
5. Under **They join as**, choose the role everyone in this invite receives. New invites default to **Editor**.
6. Click **Invite to Base**.

<Callout type="info">
  You can only assign roles that are at most equal to your own role on the base.
</Callout>

<img alt="The Base Members pane under Base Settings" src={__img0} placeholder="blur" />
<img alt="The Add Member to Base dialog" src={__img1} placeholder="blur" />
<img alt="Entering an address and choosing the role they join as" src={__img2} placeholder="blur" />

The same dialog offers **Invite via private link** as an alternative to inviting one address at a time: choose a role, click **Create an invite link**, and anyone who opens the link can redeem it to join this base. Joining a base through a link grants access to that base only. See [invite links](/docs/product/collaboration/invite-links) for restricting a link to an email domain, managing several links, and deleting one.

Workspace members inherit the role assigned at the workspace level unless a specific role is set at the base level. You can also invite users directly to a base without broader workspace access — ideal for external partners or temporary contributors.

## Invite Teams to Base ☁

1. Open the base and go to **Base Settings** → **Invite** → **Members**.
2. Click **Add Teams**.
3. Select one or more teams from the dropdown.
4. Choose a role — **Editor**, **Commenter**, **Viewer**, or **No Access**.
5. Click **Add Teams**.

<Callout type="info">
  Teams cannot be assigned the 

  **Owner**

   role at the base level. When a team is invited, all its members inherit the assigned base-level role unless overridden by an individual role.
</Callout>

<img alt="Picking a team in the Add Teams to Base dialog" src={__img3} placeholder="blur" />
<img alt="The Add Teams dialog ready to confirm" src={__img4} placeholder="blur" />

To learn more about creating and managing teams, refer to the [Teams documentation](/docs/product/collaboration/teams).

## List Base Members and Teams

The **Members** page displays all users and teams with access to the base, including their role and date joined. Roles inherited from the workspace are labelled **Role inherited from workspace**.

<img alt="The Base Members list showing members and a team" src={__img5} placeholder="blur" />

## Modify Roles for Members or Teams

1. Click the role dropdown next to the member or team.
2. Select a new role — **Owner**, **Creator**, **Editor**, **Commenter**, **Viewer**, **App User**, **No Access**, or **Inherit**. Each option carries a one-line description, and the change takes effect immediately.

<img alt="Changing a member's base role" src={__img6} placeholder="blur" />

<Callout type="info">
  You can only assign roles that are at most equal to your own role on the base.
</Callout>

## Role Precedence

When a user has multiple role assignments through both team and individual access:

* Individual explicit role takes precedence over team-assigned role.
* Base-level roles override workspace-level roles.
* In case of multiple team roles, the **highest** permission applies.

Learn more about [effective role resolution](/docs/product/collaboration/teams#effective-role-resolution).

## Remove or Revoke Base Access

### Deny Access

To block a user or team from accessing the base:

* Click the role dropdown next to the member or team.
* Select **No Access**.

### Revoke Explicit Assignment

To remove a base-level role and fall back to workspace or team inheritance:

* Click the role dropdown next to the member or team.
* Select **Inherit**.

<Callout type="info">
  Use 

  **No Access**

   to explicitly block access. Use 

  **Inherit**

   to remove the base-level assignment and fall back to workspace or team role.
</Callout>

## Availability

* Teams are available on **NocoDB Cloud** (Business plan and above) and licensed self-hosted deployments (Scale plan and above).

## Related

* [Roles and permissions](/docs/product/collaboration/roles-and-permissions)

---

## Related pages

- [Create Base](https://nocodb.com/docs/product/bases/create-base.md): Learn how to create a base in NocoDB.
- [Folders](https://nocodb.com/docs/product/bases/folders.md): Organize tables, documents, and dashboards into collapsible folders in the base sidebar.
- [Import Airtable to NocoDB](https://nocodb.com/docs/product/bases/import-base-from-airtable.md): A complete import of your Airtable base to NocoDB within minutes
- [Share Base](https://nocodb.com/docs/product/bases/share-base.md): Procedures to share a base & generating embedded iframe
- [Base Snapshots](https://nocodb.com/docs/product/bases/snapshots.md): Procedures to create and manage snapshots
- [Base Trash ☁](https://nocodb.com/docs/product/bases/base-trash.md): View, restore, and permanently delete trashed items — records, tables, views, fields, dashboards, widgets, workflows, scripts, and extensions — from a single base-level Trash.
- [Trash Settings ☁](https://nocodb.com/docs/product/bases/trash-settings.md): Configure per-table trash retention and disable trash on a per-table basis.
- [Private Base](https://nocodb.com/docs/product/bases/private-base.md): Learn how to configure and manage access to Private Bases in NocoDB.