Team & Roles
Invite teammates and control access at both the organization and agent level
An organization is a shared space — agents, integrations, secrets, traces, and billing all live inside it. Access works at two levels: a member's organization role sets their baseline, and agent collaborators can grant tighter or looser access on individual agents.
Invite a teammate
- Open Settings → Team Management.
- Click Invite Member.
- Enter their email and pick a role.
- Send Invitation.
The invitee gets an email link that auto-creates their account if they don't already have one.
Organization roles
Two organization-level roles:
- Admin — full access to the organization: manage members, billing, and every agent.
- Member — can collaborate on agents in the organization. Per-agent access is controlled by collaborator roles (see below).
Use Admin sparingly — it includes billing and the ability to manage every other member.
Agent collaborators
Each agent has its own collaborator list with three roles:
- Admin — full control over the agent, including managing collaborators on it.
- Editor — build, edit prompts and flow, attach tools and knowledge, and deploy.
- Viewer — read-only access to the agent, traces, and conversations.
Adding someone as a collaborator on an agent gives them that level of access regardless of their org role (other than Admin, which always has full access).
Manage members
In Team Management you can:
- Change role — promote or demote any member.
- Remove — revokes access immediately.
- Resend invitation — for invitations that expired before acceptance.
- Revoke pending invitation — pulls back an unaccepted invite.
What members share
Everything in an organization is potentially accessible — agents, integrations, secrets, knowledge base, traces, conversations, evaluations — subject to org and per-agent collaborator roles.
If you need hard isolation between teams or environments, use separate organizations. A user can belong to many organizations and switch between them.
Multi-organization patterns
| Pattern | Use it for |
|---|---|
| One organization, all envs | Tiny teams. Quick start. |
| Dev / Prod organizations | Most teams. Different secrets, different members. |
| Per-team organizations | Larger orgs. Each team owns its organization; cross-team agents share via API. |
| Per-customer organizations | Agencies/consultancies running agents on behalf of clients. |
Best practices
- Treat team management as security. Removing a departing teammate is a security action — do it the same day.
- Don't share accounts. Every human gets their own login.
- Use API keys for automation. Don't burn a human seat on a script. (Settings → API Keys)