# Organization Teams

> Part of the NocoDB documentation (Product docs > Teams). 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/teams/organization-teams
Last updated: 2026-10-03

NocoDB organization teams are managed from the Admin Panel, and you can give them roles in any workspace of the organization.

Organization teams have the entire organization as their scope. You can give them roles in any workspace of the organization. The Org Admin creates and manages them in **Admin Panel** > **Teams**.

Org teams do not have the Team Owner and Team Member roles of workspace teams. The **Org Admin** has full control of all org teams. The Org Admin can create, edit, and delete teams, and manage their members.

In workspace member and team lists, org teams show an **ORG** badge. They are read-only in a workspace. You cannot edit their members from workspace settings. You can give them workspace or base roles, the same as workspace teams.

## Create an Org Team

1. Go to **Admin Panel** > **Teams**.
2. Click **+ New Team**.
3. Enter a team name.
4. Optional: to create the team as a sub-team, select a **Parent team**.
5. Click **Create Team**.

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

## Manage an Org Team

Next to a team, click the **Actions** (three dots) menu. The menu has these options:

| Option           | What it does                                       |
| ---------------- | -------------------------------------------------- |
| **Edit**         | Opens the team to manage its members and settings. |
| **Add sub-team** | Creates a nested sub-team below this team.         |
| **Move team**    | Moves the team below a different parent.           |
| **Delete team**  | Removes the team from the organization.            |

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

## Add Members to an Org Team

1. In **Admin Panel** > **Teams**, click **Edit** on the team.
2. Click **Add Members**.
3. From the member list of the organization, select one or more members.
4. Click **Add Members** to confirm.

The list marks members that are already in the team, and you cannot add them again. To find a user, search by name or email.

## Sub-teams

Org teams use the same hierarchy as workspace teams. You can nest sub-teams up to **4 levels deep**.

To create an org sub-team:

1. In **Admin Panel** > **Teams**, next to the parent team, click the **Actions** (three dots) menu.
2. Select **Add sub-team**.
3. Enter a name.
4. Click **Create Team**.

You can also click **+ New Team** and select a parent team in the **Parent team** list.

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

<Callout type="warning">
  Organization teams and workspace teams are separate hierarchies. An org team cannot be a child of a workspace team, and a workspace team cannot be a child of an org team.
</Callout>

## Assign Org Teams to Workspaces and Bases

You can give an org team a workspace role or a base role, the same as a workspace team. When an org team gets a role, all its members get that access.

On the **Members** page of a workspace, org teams show an **ORG** badge. You can give or change their role on this page. You cannot edit the members of the team here. You manage the members from the Admin Panel.

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

Roles of org teams follow the same [effective role resolution](/docs/product/collaboration/teams#effective-role-resolution) rules as workspace teams.

## Org Teams vs Workspace Teams

| Aspect                    | Workspace Teams                      | Organization Teams                    |
| ------------------------- | ------------------------------------ | ------------------------------------- |
| Plan required             | Cloud Business+ / self-hosted Scale+ | Cloud Enterprise / self-hosted Scale+ |
| Scope                     | Single workspace                     | Entire organization                   |
| Managed from              | Workspace sidebar > Teams            | Admin Panel > Teams                   |
| Managed by                | Team Owners                          | Org Admin                             |
| Visible in workspace      | Yes (native)                         | Yes (with ORG badge, read-only)       |
| Sub-team depth            | 4 levels                             | 4 levels                              |
| Members source            | Workspace members                    | Org members                           |
| Can parent the other type | No                                   | No                                    |

<Callout type="info">
  Team names are scoped — they must be unique within their own scope (workspace or org), but the same name can exist in different scopes. For example, a team called "Support" can exist as an org team and also as a workspace team in two different workspaces, all independently.
</Callout>

## Best practices

* **Use org teams for cross-workspace access.** If a team needs the same roles in many workspaces, create an org team in the Admin Panel. Do not make copies of a workspace team in each workspace.
* **Keep workspace teams for project-specific groups.** If a team needs access in one workspace only, a workspace team is easier to manage.

## Availability

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

---

## Related pages

- [Sub-Teams](https://nocodb.com/docs/product/collaboration/teams/sub-teams.md): NocoDB sub-teams nest up to four levels deep: roles flow upward, and table, record and field permissions flow downward.