Admin controls
Enable / disable agents, manage custom agents, and use the 20-agent cap.
Admins only. Members can run and observe; only admins can edit.
Admins control which agents are available to the org from /admin/agents. Two surfaces: enable/disable for catalog agents, and full CRUD for custom agents.
The agents table
The agents table has one row per agent — catalog agents listed first, custom agents below. Each row shows the agent's name, status, and available actions. The footer displays a counter: N / 20 custom agents.
Enabling / disabling
Catalog agents — toggle to enable or disable. Disabled catalog agents disappear from the AgentForce hub for members and return a "This agent is unavailable" page if accessed directly via /agentforce/{slug}/chat.
Custom agents — status is live, draft, or disabled. Draft agents only appear to admins on /admin/agents and in the test panel. Live agents are visible to all members. State changes take effect immediately.
Disabling an agent does not delete it. Existing thread history is preserved and accessible again if you re-enable.
Creating, editing, deleting
Click + New agent to open the create dialog, then complete the form to land on the editor at /admin/agents/{slug}/edit.
Edits in the editor are saved as drafts until you click Publish. See Versions and publishing for how draft and live versions relate.
Delete requires typing the agent's display name to confirm. This removes the agent and its configuration permanently. Catalog agents cannot be deleted — only disabled.
Defaults
All 4 catalog agents are enabled for new orgs by default. New custom agents start as live and become visible to members immediately on publish.
Per-org isolation
Status and custom-agent configuration are per-org. If you administer multiple orgs, settings in one do not affect the others.
Audit
The Activity sheet on the agent editor logs draft saves, publishes, restores, and resets — each entry includes the actor and timestamp. For workspace-wide audit, contact your account team.