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

Invite members and teams to a NocoDB workspace, change their workspace roles, and remove them.

## Invite Members to Workspace

1. In the workspace sidebar, click **Invite Members**. The **Members** page opens.
2. Click **Add Members**. The **Invite to Workspace** dialog opens.

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

3. Click the field below **Invite specific people**.
4. Type one or more email addresses.
5. Below **They join as**, select a role. All people in this invite get this role.
6. 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 same dialog also has **Invite via private link**. This creates a link, so you do not have to invite one address at a time. Anyone who opens the link can use it to join the workspace with a role that you select. To create a link, you need the **Editor** role or higher.

For more information, refer to [invite links](/docs/product/collaboration/invite-links).

## Invite Teams to Workspace ☁

You can invite teams to a workspace. All members of the team get the workspace role that you give the team.

1. In the workspace sidebar, click **Invite Members**. The **Members** page opens.
2. Click **Add Teams**. The **Add Teams to Workspace** dialog opens.
3. From the dropdown, select one or more teams. The list shows the number of members in each team.

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

4. Below **They join as**, select the role for the teams.

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

5. Click **Add Team**. If you select more than one team, the button shows **Add Teams**.

<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 create and manage 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 shows all users and teams that have access to the workspace.

| Column             | What it shows                                                                                                                                                                    |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Members**        | For a member: the name and the email. For a team: the name and the number of members. Organization teams have an **ORG** badge, which makes them different from workspace teams. |
| **Workspace role** | The workspace role of the member or team.                                                                                                                                        |
| **Billable**       | A crown if the member uses a paid seat.                                                                                                                                          |
| **Date Joined**    | The date that the member joined the workspace.                                                                                                                                   |
| **Actions**        | A menu to remove the member or team.                                                                                                                                             |

The page header shows the number of paid seats that the workspace uses. On Community Edition and on unlicensed self-hosted deployments, the **Billable** column and the seat count show **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 shows a member who uses a paid seat. A member uses a paid seat when the member has **Editor** or a higher role in one of these places:

* the workspace
* a base
* an interface

For example, a member who is **Viewer** in the workspace is still billable if that member is **Editor** in one base. To see the assignment that makes a member billable, click the crown.

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

## Modify Roles for Members or Teams

You can change the roles of members and teams on the **Members** page.

1. In the **Workspace role** column, click the role dropdown next to the member or team.
2. Select a new role. Each role shows a one-line description. A check mark shows the current role.

<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

A user can get roles from more than one source, as a member and through teams. NocoDB uses these rules to find the role that applies:

| The user has                       | The role that applies     |
| ---------------------------------- | ------------------------- |
| An individual role and a team role | The individual role       |
| A workspace role and a base role   | The base role             |
| Roles from two or more teams       | The **highest** team role |

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

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

## Remove Members or Teams from Workspace

To remove a member or team from the workspace, use the actions menu.

1. In the **Actions** column, click the vertical ellipsis `⋮` next to the member or team.
2. Select **Remove member** or **Remove team**.

The menu also shows the user ID of the member or the ID of the team. Click the copy button to copy the ID 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. Each user then gets access from their team roles and base roles.
* Make teams for departments or work groups, to manage roles with less work.
* In large workspaces, change team permissions, not the roles of single members.

For more information, refer to [Teams best practices](/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): Invite members and teams to a NocoDB base, change their base roles, and remove or block their access.
- [Invite Links](https://nocodb.com/docs/product/collaboration/invite-links.md): Create, share, restrict and delete NocoDB invite links that let people join a base or a workspace.