Teams
Last updated: March 2026
Organize your workspace members into teams with hierarchical structure. Teams control data visibility through permission scopes and help manage large organizations with departments and sub-teams.
Creating teams
Teams group workspace members into organizational units. Each team has a name, optional description, and can belong to a parent team, creating a hierarchical structure that mirrors your company organization. For example, you might have a "Sales" parent team with "Enterprise Sales" and "SMB Sales" as child teams.
The Teams workspace provides a visual manager for creating and organizing your team structure. From here, you can create new teams, assign members, and arrange the hierarchy.
Open the Teams workspace
Navigate to the Teams section from the workspace sidebar. The team manager shows your current team structure.
Create a new team
Click "New Team" and enter a name and description. Optionally select a parent team if this is a sub-team within a larger department.
Add members
Select existing workspace users to add to the team. Each member has a role within the team (e.g., member, leader). Users can belong to multiple teams.
Use teams to reflect your organizational structure. This makes it easier to set up permissions that automatically apply to the right groups of people.
Team hierarchy
Teams support a parent-child relationship through the parentTeamId field. This creates a tree structure where child teams inherit context from their parent. The team manager displays this hierarchy visually, showing nested teams with member counts at each level.
Hierarchy is especially important for the "team" permission scope. When a user has "team" scope on an entity, they can access records owned by anyone in their team or in any child team below them. This means a Sales Director in the parent "Sales" team can see records from both "Enterprise Sales" and "SMB Sales" sub-teams.
Team hierarchy affects permission scopes. The "team" scope in permissions includes the user's team and all descendant teams. Plan your hierarchy to match your data access requirements.
Member management
Each team member has a user reference and a role within the team. You can view team details including the full member list, child teams, and parent team. Members can be added or removed at any time, and changes take effect immediately for permission calculations.
The team detail view shows user information including name, email, and avatar. The member count is tracked at both the team level and across child teams, giving you a quick overview of team sizes throughout your organization.
| Property | Description |
|---|---|
| Name | The display name of the team |
| Description | Optional text describing the team purpose |
| Parent team | The parent team in the hierarchy (null for top-level teams) |
| Members | Users assigned to this team with their team role |
| Child teams | Sub-teams nested under this team |
| User count | Total number of members directly in this team |
Teams and permissions
Teams integrate directly with the permission system through the "team" scope. When you create a permission rule with scope "team", users can only access records that belong to members of their team (or descendant teams). This is more restrictive than "tenant" (all records) but broader than "own" (only your records).
For example, you might set the "Contacts" entity to have "team" read scope for the Sales role. Each salesperson can then see contacts owned by anyone on their team, but not contacts belonging to other teams. A team leader with access to the parent team can see contacts across all child teams.