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. On the Teams page, 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. On the Teams page, 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