Teams

Teams let you partition your workspace’s agents and users into logical units—by department, project, or however makes sense for you. Each team can have its own administrators, capability settings, and member access controls.

​

When to use teams

Teams are optional and work best for workspaces that need:

• Departmental boundaries: Different departments working with different agents
• Delegated administration: Let team leads manage their own agents without full admin access
• Capability controls: Restrict certain integrations to specific teams
• Cleaner organization: Keep the agent list manageable as you scale

For smaller workspaces where everyone works with the same agents, you can skip teams entirely.

​

How teams work

When teams are enabled, agents and users are organized into teams. Each user can belong to multiple teams with different roles in each. Each team also has its own document library for files that should be shared within the team but not the whole workspace.

​

User roles

Workspace-level roles: Team-level roles:

​

Creating agents with teams

When you create a new agent, you’ll choose which team it belongs to. If you only have one option (a single team with global agents disabled), the agent is assigned automatically without showing a dropdown.

​

Managing teams

Managing teams happens in two places:

• Teams page: A card-based overview of every team you have access to. Each card shows the team’s member and agent counts plus its monthly credit usage, with a “Team admin” badge highlighting teams where you can manage settings. Click a card to open the team’s home page.
• Team home page: Lists the people, agents, and shared documents that make up the team, and is also where all team-level admin actions live.
  • The People & Agents tab shows members, pending invites, and (for workspace admins) support-access users as cards in one grid — not separate tables. Use the search field to find someone by name or email, or type support, invite, pending, or expired to focus on those cards. All, People, and Agents filter chips narrow which section is visible.
  • Any member can remove themselves with the Leave team button in the page header — unless they are the team’s only admin, in which case another admin must be appointed first.
  • Team admins (and workspace admins) get Invite and Add existing on the People header, plus per-card controls to change roles and remove members. Pending and expired invitations appear as cards in the same grid; expired invites are hidden by default — use Show next to the People heading to reveal them, then Resend or Revoke as needed.
  • Workspace admins also get a settings kebab menu in the page header to Rename the team or Delete the team. Monthly credit limits and other team settings live on the Settings tab. (Team admins can manage their team’s people but not the team’s existence or budget.)
  • If your workspace has active support access, support users assigned to a team appear in the people grid with an expiry line; workspace admins can revoke access from the card. The People heading shows a separate support count badge when support users are present.

Workspace admins can create new teams from the workspace-wide teams overview. (Documentation for that flow lives on the Workspace page in the product.)

​

Team capabilities

Each team can have its own capability settings that override the workspace defaults. This lets you:

• Enable integrations for a specific team that are off by default
• Restrict certain capabilities to authorized teams only
• Set different defaults for different teams

This is done on the Capabilities page, which has a section per team in addition to the workspace-wide defaults.

​

Team-specific capabilities

Some capabilities are designed specifically for teams:

• Team Analytics — Gives team admins visibility into their team’s usage metrics, member activity, and agent performance, scoped to their team.
• Team Explorer — Provides read-only access for team admins to browse documents and data across agents within the team.

These capabilities are scoped to the team and respect admin restriction tiers — they’re only visible to users at the required admin level.

​

Global agents

Agents that don’t belong to any team are called “global agents.” Your workspace can control who can create these:

• Everyone: Any user can create global agents
• Admins only: Only workspace administrators
• Nobody: All agents must belong to a team

Global agents appear in a separate section and are only visible to workspace administrators.

​

FAQ

​

Learn more