Teams

Overview

Teams let you group members so you can assign and manage permissions at scale. Instead of configuring the same role for each person on every base, add users to a team and grant that team a role on one or more bases.

NocoDB supports two scopes of teams:

When to use which:

• Org teams are ideal for company-wide groups like departments (Engineering, Marketing, HR) that need consistent access across multiple workspaces. The Org Admin manages them centrally, and they can be assigned roles in any workspace.
• Workspace teams are better for project-specific or workspace-local groups — for example, a "Sprint Team" or "External Contractors" group that only needs access within a single workspace.

Teams help you to

• Organize members by department, project, or function
• Manage permissions efficiently by assigning roles to teams instead of individuals
• Scale access control without managing individual user permissions
• Maintain flexibility with inheritance and override capabilities
• Create sub-teams for more granular organization with up to 4 levels of nesting

Workspace Teams

Create Team

1. Navigate to Workspace Settings > Teams tab.
2. Click New Team.
3. Enter a team name (Optional).
4. Click Create Team.

When a team is created, the creator is automatically added as its first member and designated as the Team Owner. Team Owners have full administrative privileges, including adding or removing members, renaming the team, and deleting it when necessary. Multiple owners can be assigned to a team, but each team must always have at least one owner.

Add Members to a Team

In the Teams tab, select the team you want to manage, then follow these steps:

1. Click Add Members.
2. Use the toggle buttons to select existing workspace members to add. Members already part of the team are clearly indicated.
3. Click Add Members again to confirm your selection.

You can search by name or email to quickly locate users. Existing team members have their toggles disabled to avoid duplicate additions. Each member's workspace role is displayed beside their name for better context.

Remove Members from a Team

In the Teams tab, select the team you want to manage, then follow these steps:

1. Locate the member you want to remove. Use the search bar if needed and open the Actions (three dots) menu beside their name.
2. Select Remove Member.
3. Confirm the action when prompted.

To remove multiple members at once:

1. Use the checkboxes to select the members you want to remove.
2. Click Actions > Remove from Team at the top of the member list.
3. Confirm the action when prompted.

Manage Team Owners

A team can have multiple owners, but it must always have at least one.

To add or remove team owners:

1. In the Teams tab, select the team you want to manage.
2. Locate the member whose ownership status you want to change. Use the search bar if necessary and open the Actions (three dots) menu beside their name.
3. To grant ownership, select Assign as Team Owner. To revoke ownership, select Remove as Team Owner.

Leave Team

Members can leave a team on their own if they no longer wish to be part of it (any team member can leave, not just owners — as long as at least one owner remains).

To leave a team you are a member of:

1. In the Teams tab, open team context menu by clicking the Actions (three dots) button beside the team name.
2. Click the Leave Team button from the dropdown menu.
3. Confirm the action when prompted.

Rename Team

In the Teams tab, select the team you want to rename. Edit team name as needed, and your changes will be saved automatically.

Delete Team

To delete a team:

1. In the Teams tab, open team context menu by clicking the Actions (three dots) button beside the team name.
2. Click the Delete Team button from the dropdown menu.
3. Confirm the action when prompted.

Sub-teams

You can create teams within teams to match how your company is organized. For example, an "Engineering" team can have "Frontend" and "Backend" as sub-teams.

Sub-teams can be nested up to 4 levels deep.

Engineering
├── Frontend
│   └── Design System
│       └── Icons              ← maximum depth
└── Backend

Create a sub-team

1. In the Teams tab, click the Actions (three dots) menu next to the parent team.
2. Select Create Sub-team.
3. Enter a name for the sub-team.
4. Click Create Team.

Alternatively, click New Team and select a parent team from the Parent team dropdown. Enter a name for the team and click Create Team.

Move a team

You can move a team under a different parent, or make it a top-level team.

1. In the Teams tab, click the Actions (three dots) menu next to the team.
2. Select Move Team.
3. Pick the new parent team, or choose no parent to make it top-level.
4. Confirm the move.

Members in sub-teams

Adding someone to a parent team does not automatically add them to its sub-teams. You manage each team's members separately.

When you open a team's details, you'll see:

• Direct members — people you added to this team
• Inherited members — people from parent teams above, shown for reference with a label indicating which team they belong to

How sub-teams affect permissions

Sub-teams change how permissions work in two ways:

1. Workspace & base roles flow upward

When you give a sub-team a role on a workspace or base, members of the parent team also get that role automatically. This way, managers in the parent team can always see what their sub-teams have access to.

Example: The "Frontend" sub-team has Editor access to Workspace X.

2. Table, record & field permissions flow downward

When you grant a team access using "Specific users or teams" in table visibility, record permissions, or field permissions, you can choose whether to include sub-team members or not.

After selecting a team, you'll see a segmented control next to the team name with two options:

Example: The "Infrastructure" table is visible to the "Engineering" team.

With "Include sub-teams" (default):

With "This team only":

This toggle is available wherever you see the "Specific users or teams" option:

• Table visibility — who can see a table
• Record permissions — who can create or delete records
• Field permissions — who can edit a field

Team roles

Every team member is either an Owner or a Member.

• The person who creates a team is automatically its first Owner.
• A team can have multiple Owners but must always have at least one.
• Team roles (Owner/Member) are separate from workspace and base roles (Creator, Editor, Viewer, etc.).

Assign roles to teams

You can give a team a role at the workspace or base level, just like you do for individual users. When a team gets a role, all its members receive that access.

Available roles for teams:

• Creator — full control except deletion
• Editor — add, edit, and delete records
• Commenter — view and comment on records
• Viewer — read-only access
• No Access — block access entirely

For step-by-step instructions:

• Add a team to a workspace
• Add a team to a base

Effective role resolution

When someone belongs to one or more teams and has an individual role, NocoDB picks the one that applies using this order:

For a base

For a workspace

Rules to remember

• Individual roles always win over team roles at the same level.
• Base-level roles win over workspace-level roles — a role set on a specific base takes priority.
• Highest team role wins — if you're in two teams with different roles, you get the higher one. For example, Viewer + Editor = Editor.
• "Inherit" at workspace level means "use my team role." Any other workspace role overrides team roles.
• "No Access" at workspace level blocks everything — even team roles can't override it.

Examples

Team role only

Alice is in the "Marketing" team, which has Editor access on Workspace X. Alice has no individual role.

→ Alice gets Editor access on the workspace and all its bases.

Individual role overrides team

Bob is in "Marketing" (Editor on Workspace X), but Bob is also individually set as Viewer on Workspace X.

→ Bob gets Viewer — individual roles always take priority, even if less permissive.

Multiple teams

Carol is in "Marketing" (Viewer on Base A) and "Content" (Editor on Base A).

→ Carol gets Editor on Base A — the higher team role wins.

Base-level override

Dave is in "Engineering" (Editor on Workspace X). He's also individually set as Creator on Base B.

→ Dave gets Creator on Base B, Editor on all other bases.

Sub-team role flowing upward

"Frontend" is a sub-team of "Engineering." "Frontend" has Editor on Workspace X.

→ Frontend members get Editor. → Engineering members also get Editor — parent team members automatically receive sub-team roles.

Best practices

• Invite users with the "Inherit" role at workspace level. This lets their access be fully controlled through teams. (Note: "No Access" at workspace level blocks all team roles.)
• Match your org chart — create top-level teams for departments and sub-teams for groups within them.
• Put managers in parent teams — they'll automatically get access to everything their sub-teams can see.
• Use individual roles only for exceptions — teams should handle the norm, individual assignments handle the edge cases.
• Use clear team names (e.g., Eng - Backend, Ops - HR) so it's easy to find and manage teams.
• Review membership regularly — remove people who've left or changed roles.
• Add multiple team owners — so things don't get stuck if one owner is unavailable.

Organization Teams

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.

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.

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.

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.

From a workspace's Members tab, 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.

Roles assigned to org teams follow the same effective role resolution rules as workspace teams.

Org Teams vs Workspace Teams

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.