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.

​

Sharing an agent with other teams

An agent normally stays inside its own team. To let others use it, open the agent’s Settings → User access → Beyond [team] panel and pick either selected teams or the entire workspace. The agent keeps its own team, and its credit usage is always counted there. People reached this way can chat with the agent and trigger it, but never edit it — see Access control for how this combines with the agent’s other access rules.

​

Managing teams

Managing teams happens in a few places:

• Workspace Members list: Workspace admins (and team admins, for teams they admin) can manage an existing person’s teams from their row — Manage teams in Actions, or the Add / Edit chip next to their team badges. The picker shows current teams (remove or change role) and lets you add more, using the same control as when inviting someone new.
• 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. Search by team name, pick a person to see only the teams they belong to, show or hide teams without members, or filter by tags. 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 someone holds the support role on your workspace, they count as a member of every team and appear in the people grid with an expiry line; workspace admins can revoke the role 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
• Choose which capabilities new agents in the team start with
• Give a capability extra instructions that apply to every agent in the team
• Set default or locked values for a capability’s settings, such as requiring approval for outgoing email

This is done on the Capabilities page. Pick the workspace or a team at the top, then click a capability to open its panel: availability, whether new agents start with it, the production-only marking, default and locked settings, and extra instructions are all edited there. A team’s instructions replace the workspace ones, and the team inherits the workspace text when it has none of its own.

​

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, except restricted and personal agents.

These capabilities are scoped to the team and only work on admin-only agents at the team admin level, so only team and workspace admins can use them.

​

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 are not hidden by the Teams feature. Anyone in the workspace can see and use them according to the agent’s own access settings — the Workspace access default (for Admins, Creators, and Collaborators) plus any named-people rules — exactly as if the workspace had no teams. On the Agents page they are listed under a separate Global agents heading. In the Agent management view, only workspace admins see global agents; team admins see only their own teams’ agents.

​

Personal agents

Sometimes an agent works for one person rather than a team — an email assistant, an executive overview agent connected to someone’s own mailbox, a sounding board that knows your role and company, or an experiment you’re not ready to share. Personal agents let people keep such agents in the company workspace, where they can still use the workspace’s integrations and talk to other agents, without putting them in a shared team. Every person has their own personal team, which holds only their personal agents. A personal agent:

• Only for the people it names: only the owner, and the people they add by name under Settings → User access, can see and use it. Others can get Use or Edit access, but a personal agent has only one owner. For example, an executive can give their assistant Use access to their personal agent.
• Outside the shared teams: team admins don’t see it. It follows the capability rules workspace admins set for personal agents (see below), and uses the workspace document library plus its own documents.
• Listed under Personal agents: on the Agents page, your personal agents have their own section. Personal agents someone has shared with you appear under that person’s name.
• Talks to other agents: by default, only your other personal agents can reach it. Agents set to be discoverable by everyone can be called from a personal agent as usual.

To create one, choose Personal as the team when creating, importing, or cloning an agent. To turn an existing agent into a personal agent, its owner can use Move to team on the agent card and pick Personal; from then on only the people named on it can open it, and anyone else who owned it keeps Edit access. A personal agent can be moved into a team the same way when others should start using it. Workspace admins manage personal agents only from the outside: they see who owns one and who else has access, its description, value statement and key metrics, which capabilities and integrations it has, and what it costs. They can disable it, limit its credits, change its model or lifecycle phase, or delete it, but can’t see its instructions, chats or documents, move it, or change its other settings. Team admins don’t see personal agents at all. See Personal and restricted agents.

​

Managing personal agents

Workspace admins control personal agents in three places:

• Workspace → Settings → Personal agents: turn personal agents on or off, and set a monthly credit limit per person, shared by all of that person’s personal agents.
• Capabilities → Personal agents: what personal agents may use, edited like a team’s capability settings. You can switch off capabilities the workspace allows, choose which ones new personal agents start with, lock settings such as requiring approval for outgoing email, and add extra instructions.
• Agent management → Agent Limits: a daily and a monthly credit limit for a single personal agent, like for any other agent.

​

FAQ

​

Learn more