Opidocs
GuidesAgentForce guides

Manage agents for your org

Enable, disable, and keep track of your org's agents.

Advanced · ~10 min · Prerequisites: admin access

Building and editing agents is admin-only. Members can run and observe agents, but only admins can create or change them.

What you'll do

Use the agent admin console to control which agents members can see, stay under the 20-agent cap, and track changes through the activity log.

Open agent admin

Go to /admin/agents. This is your central control panel for every agent in the org — catalog agents, custom agents you've built, and drafts in progress. Each row shows the agent's name, status (published, draft, disabled), and the last time it was modified.

For the full breakdown of admin controls, see Admin controls.

Enable or disable agents

Any published agent can be disabled without deleting it. Disabling hides it from the hub so members can't open new conversations with it — existing threads are preserved. Re-enabling it makes it visible again immediately.

To disable: click the agent row → open the ... menu → Disable. To re-enable: same menu → Enable.

Use disabling to:

  • Temporarily pull an agent that's producing bad results while you fix its instructions.
  • Decommission a catalog agent your org doesn't use (e.g. hiding Content Creator if your team doesn't need it).
  • Run a staged rollout: build and test a new agent, then enable it once you're confident.

Note that the four default catalog agents (Customer Support, Sales Assistant, Research Analyst, Content Creator) can be disabled but not deleted.

Track the 20-agent cap

Your org can have up to 20 custom agents at once. The N / 20 counter in the top-right of the agents admin page shows how many slots are in use.

Drafts count toward the cap. If you're close to the limit and need to build a new agent, disable or delete a draft that's no longer needed to free a slot.

The four default catalog agents do not count toward the cap.

Audit changes

Every create, edit, publish, enable, and disable action is recorded in the activity log. Open it from the agents admin page → Activity log. Each entry shows who made the change, what they changed, and when.

Use the activity log to:

  • Track down why an agent started behaving differently (someone edited its instructions).
  • Confirm a publish happened when expected.
  • Review who enabled or disabled an agent.

Try this next

On this page