# Workspace Collaboration

> Part of the NocoDB documentation (Product docs > Users). 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/workspace-collaboration
Last updated: 2026-09-25

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

## Invite Members to Workspace

1. Click **Invite Members** in the workspace sidebar to open the **Members** page.
2. Click **Add Members** to open **Invite to Workspace**.

<img alt="The Invite to Workspace dialog" src={__img0} placeholder="blur" />

3. Click the field under **Invite specific people** and enter one or more email addresses.
4. Under **They join as**, choose the role everyone in this invite receives.
5. Click **Invite to Workspace**.

<img alt="Entering addresses and choosing a role" src={__img1} placeholder="blur" />

<img alt="The role dropdown" src={__img2} placeholder="blur" />

<Callout type="info">
  Any user can invite members to the workspace, but they can only assign a role that is at most equal to their own role.
</Callout>

<Callout type="info">
  On paid plans, 

  **Editor**

   and above consume a paid seat, and the dialog warns you with 

  **Additional charges may apply for new invites**

   before you confirm. 

  **Commenter**

  , 

  **Viewer**

   and 

  **No Access**

   do not.
</Callout>

## Invite via Link

The dialog also offers **Invite via private link**, which creates a link anyone who opens it can redeem to join the workspace at a role you choose, rather than inviting one address at a time. Creating a link requires the **Editor** role or above.

Learn more about [invite links](/docs/product/collaboration/invite-links).

## Invite Teams to Workspace ☁

Teams can be invited to a workspace for simplified collaboration, with a workspace-level role assigned to all team members.

1. Click **Invite Members** in the workspace sidebar to open the **Members** page.
2. Click **Add Teams** to open **Add Teams to Workspace**.
3. Select one or more teams from the dropdown. Each is listed with its member count.

<img alt="Selecting teams to add" src={__img3} placeholder="blur" />

4. Under **They join as**, choose the role the selected teams receive.

<img alt="Choosing the role the teams join with" src={__img4} placeholder="blur" />

5. Click **Add Team**, or **Add Teams** when more than one is selected.

<img alt="The dialog ready to confirm" src={__img5} placeholder="blur" />

<Callout type="info">
  **Owner**

   is listed but cannot be picked for a team, and 

  **Inherit**

   is not offered. You can only assign roles that are at most equal to your own role.
</Callout>

<Callout type="info">
  When a team is invited, all users under that team inherit the assigned workspace-level role unless overridden by an explicit workspace role or base-level role.
</Callout>

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

<Callout type="info">
  **Organization Teams**

   are available on 

  **NocoDB Cloud**

   (Enterprise plan) and licensed self-hosted deployments (Scale plan and above). Org-level teams also appear in the team selector with an 

  **ORG**

   badge. These teams are managed from the 

  [Admin Panel](/docs/product/account-settings/cloud-enterprise-edition/admin-panel#teams)

   and are read-only at the workspace level, so you cannot edit their membership from workspace settings, but you can assign them workspace or base roles. Learn more about 

  [Organization Teams](/docs/product/collaboration/teams/organization-teams)

  .
</Callout>

<img alt="An organization team shown with an ORG badge" src={__img6} placeholder="blur" />

## List Workspace Members and Teams

The **Members** page displays all users and teams that have access to the workspace.

* Individual members appear with their name, email, role, and date joined.
* Teams are listed with their name, member count, and assigned role.
* Organization teams are shown with an **ORG** badge, distinguishing them from workspace teams.

The columns are **Members**, **Workspace role**, **Billable**, **Date Joined** and **Actions**, and the header shows how many paid seats the workspace is using. On Community Edition and unlicensed self-hosted deployments the column and the count read **Editor seat** instead.

<Callout type="info">
  The members list is accessible to all workspace members.
</Callout>

<img alt="The workspace Members page" src={__img7} placeholder="blur" />

### Why a member is billable

A crown in the **Billable** column marks a member who consumes a paid seat. Click it to see which assignment is responsible: their workspace role, any base, or any interface. A member consumes a seat when they hold **Editor** or higher in any one of those places, so someone who is **Viewer** at the workspace level can still be billable through a single base.

<img alt="The billable seat breakdown for a member" src={__img8} placeholder="blur" />

## Modify Roles for Members or Teams

Access permissions for both members and teams can be updated from the **Members** page.

1. Click the role dropdown in the **Workspace role** column beside the member or team.
2. Select a new role. Each option carries a one-line description, and the one in force is ticked.

<Callout type="info">
  You can only assign roles that are at most equal to your own role in the workspace. A team cannot be set to 

  **Owner**

   or 

  **Inherit**

  .
</Callout>

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

<img alt="Changing a team's role" src={__img10} placeholder="blur" />

## Role Precedence

When a user has multiple role assignments through both team and individual access, NocoDB resolves the final permission using a clear precedence order.

* 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.

<Callout type="info">
  This ensures users always retain the most permissive access assigned at their lowest configured level.
</Callout>

To learn more about effective role resolution, refer to the [Teams effective role resolution documentation](/docs/product/collaboration/teams#effective-role-resolution).

## Remove Members or Teams from Workspace

You can remove both members and teams from the workspace using the actions menu.

1. Click on the vertical ellipsis `⋮` in the **Actions** column beside the member or team.
2. Select **Remove member** or **Remove team**.

The menu also shows the member's user ID or the team's ID, with a button to copy it for use with the API.

<Callout type="info">
  Only the workspace 

  **owner**

   or 

  **creator**

   can remove members or teams from the workspace.
</Callout>

<img alt="Removing a member" src={__img11} placeholder="blur" />

<img alt="Removing a team" src={__img12} placeholder="blur" />

## Best Practice

* Invite all users to the workspace first with the **Inherit** role. This will allow them to access workspaces based on their team or base-level roles.
* Use teams for departments or functional groups to manage roles efficiently.
* Adjust team-level permissions instead of managing roles individually for large workspaces.

Learn more [here](/docs/product/collaboration/teams#best-practices).

## 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

- [Base Collaboration](https://nocodb.com/docs/product/collaboration/base-collaboration.md): This article explains how to invite members or teams to your base, manage their roles, and remove them when needed.
- [Invite Links](https://nocodb.com/docs/product/collaboration/invite-links.md): This article explains how to create, share, restrict and delete invite links that let people join a base or a workspace.