Agents in an Organization
Open in CMSThis page explains a foundational idea: agents belong to the organization, not to a person. Understanding this clears up most questions about access, billing, and what happens when someone leaves.
Agents are owned by the organization
When anyone in your organization creates an agent, that agent belongs to the organization — not to the individual who made it.
This has practical consequences:
| Situation | What happens |
|---|---|
| The Builder who created an agent leaves the organization | The agent stays. It was never personally theirs. |
| Credit is spent by the agent | It comes from the organization's balance, not the creator's. |
| You switch to another organization | You no longer see that agent — it lives in its own organization. |
| An Owner/Admin wants to manage any agent | They can, because the organization owns all of its agents. |
Mental model: the organization is the company; agents are company assets. People come and go, but the assets remain with the company.
Who can see and manage an agent
| Role | Access to agents |
|---|---|
| Owner / Admin | Implicit access to every agent in the organization. |
| Builder | Can build/edit only the agents they are assigned to (as a contributor). |
| No role | Can use only the agents they are assigned to (as an agent member). |
Assigning a Builder to a specific agent is done through contributors — covered next.
Where to manage agents
Open your organization: its agents are on the Agents tab.
Open the Organizations page → select your organization → Agents tab.
Each agent shows as a card (logo, kind, avatar, name, agent type) with two buttons: Open opens the agent, and Manage (Owners/Admins only) opens the agent's Manage page. Its tiles hold the tools below, plus Credit Limit and Clone. The first tile, Agent Kind, decides whether the agent is a personal or a service agent.
Deeper topics
| Topic | What it covers |
|---|---|
| Personal vs Service Agents | Whether an agent serves only you (and may use your Claude or ChatGPT subscription models) or other people. |
| Managing Agent Access | Let specific Builders contribute to an agent (contributors). |
| Transferring an Agent | Move an agent to a different organization, safely. |
| Audit Trail | Review the full history of changes made to an agent. |
| Cloning an Agent | Make a new agent with the same settings and knowledge, and see what is and is not copied. |
| Deleting an Agent | Permanently remove an agent, with a type-the-name confirmation. |
| Admin Key | Set or rotate the debug credential used for admin-level chat commands. |
Next step
Continue to Managing Agent Access.