Teams
Teams let several people work in the same workspace and share agents and tools. Manage them under Dashboard → Team.
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including managing members. One per team, cannot be changed |
| Manager | Manage members: invite, change roles, remove. Share or un-share any team resource |
| Member | Work in the team; create, share, and un-share their own agents and tools |
| Viewer | Read-only access to everything shared with the team |
Inviting people, changing roles, removing members, and revoking invitations all require Owner or Manager.
The owner's role can't be changed — including by the owner. This prevents a team from ending up with nobody who can administer it.
:::note A Manager can't act on another Manager Promoting, demoting, or removing a Manager requires the Owner. A Manager can freely manage Members and Viewers, but two Managers can't act on each other — only the Owner outranks a Manager. :::
Personal vs. team resources
Every agent and tool you create is either personal (yours alone) or owned by a team, decided when you create it. There's no in-between and nothing changes this automatically — a personal agent stays personal until someone explicitly shares it.
- Personal: only you can see or run it.
- Team-owned: every member of that team can see it; anyone who isn't a Viewer can also edit or run it.
Sharing
Sharing moves a personal agent or tool under a team, so the whole team can use it. Who can do it:
- The resource's creator can share their own work with any team they belong to.
- A team's Manager or Owner can share or un-share anything that already belongs to that team, regardless of who created it.
:::warning A Member who shares their own resource may not be able to take it back If you're a Member (not the creator) and someone else's agent or tool is shared with your team, you cannot un-share it — only the creator or a Manager/Owner of that team can. And once a Manager or Owner moves a resource between teams or back to personal, that action follows the same rule: only the creator or a Manager/Owner can undo it. Before sharing something, be sure you're comfortable with your team having lasting access to it. :::
A Viewer can never share or un-share anything — sharing is a write action.
Team LLM keys
A team can have its own LLM provider keys, managed by its Managers and Owner under Dashboard → Team. These keys are used only when a shared agent runs:
- A personal agent always uses the runner's own personal LLM keys, never a team key — even if the runner belongs to a team with keys configured.
- A shared (team-owned) agent uses the team's key for whatever provider it needs. If the team hasn't configured a key for that provider, the run falls back to the runner's personal key instead of failing outright.
This fallback exists so that sharing a working agent doesn't break it the moment it moves to a team that hasn't set up keys yet.
API keys are not shared
Unlike agents and tools, API keys are always personal — each member creates and manages their own under Settings → API keys, and there's no way to share one with a team. This is deliberate, not a missing feature: a shared key destroys attribution (you can no longer tell which teammate made a given call) and can't be revoked for one person without revoking it for everyone. If someone leaves the team or the key needs to be rotated, a personal key can be revoked without disrupting anyone else's access.
Inviting people
Invite by email from the team page. The invitee receives a link to accept.
:::warning Invitations expire after 7 days An unaccepted invitation stops working after a week — send a new one rather than resending the old link. :::
:::note Email must be configured Invitations are delivered by email. If your deployment has no transactional email provider configured, invitations are created but never delivered. :::
Leaving
Any member can leave a team. The owner cannot leave a team they own — transfer ownership or delete the team instead.