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

Organization-wide teams managed from the Admin Panel, assignable across any workspace in the org.

Organization teams are scoped to the entire organization and can be assigned roles across any workspace within the org. They are created and managed from the **Admin Panel** > **Teams** section by the Org Admin.

Unlike workspace teams, org teams do not have a separate Team Owner / Team Member distinction. The **Org Admin** has full management control over all org-level teams — including creating, editing, deleting teams and managing their members.

Org teams appear in workspace member and team lists with an **ORG** badge. They are read-only at the workspace level — you cannot edit their membership from workspace settings, but you can assign them workspace or base roles just like workspace teams.

## Create an Org Team

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

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

## Manage an Org Team

Click the **Actions** (three dots) menu beside a team to:

* **Edit** – Open the team to manage its members and settings.
* **Add sub-team** – Create a nested sub-team under this team.
* **Move team** – Move the team under a different parent.
* **Delete team** – Remove 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 you want to manage.
2. Click **Add Members**.
3. Select one or more members from the organization's member list.
4. Click **Add Members** to confirm.

Members already part of the team are indicated and cannot be added again. You can search by name or email to quickly locate users.

## Sub-teams

Org teams support the same hierarchical structure as workspace teams, with sub-teams nested up to **4 levels deep**.

To create an org sub-team:

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

Alternatively, click **+ New Team** and select a parent team from the **Parent team** dropdown.

<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

Org teams can be assigned workspace-level or base-level roles, just like workspace teams. When an org team is given a role, all its members receive that access.

On a workspace's **Members** page, org teams appear with an **ORG** badge. You can assign or change their role from this view, but you cannot edit the team's membership — that is managed from the Admin Panel.

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

Roles assigned to 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** — when teams need consistent roles across multiple workspaces, create an org team in the Admin Panel rather than duplicating workspace teams in each workspace.
* **Reserve workspace teams for project-specific groups** — if a team only needs access within a single workspace, a workspace team is simpler 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): Nest teams up to four levels deep, and understand how roles flow upward while table, record and field permissions flow downward.