Admin controls
Enabling and disabling AgentForce agents for your workspace.
In v1.0, AgentForce admin is a single decision: which of the catalog agents are turned on for your workspace. There's no per-agent personality editor, no per-user gating, no scheduling configuration. The catalog ships, you decide who's on the team.
The admin page lives at /admin/agents.
Enabling and disabling agents
The admin agents table has a row for each catalog agent with:
- The agent's name and description
- An Enabled / Disabled toggle
Toggle the switch to enable or disable the agent for the entire workspace. Changes take effect immediately:
- Enable — the agent appears on the AgentForce hub for every member
- Disable — the agent disappears from the hub. Members visiting the URL directly see a "This agent is unavailable" page
Disabling doesn't delete anything. Existing thread history is preserved; if you re-enable later, members can pick up where they left off.
When to disable an agent
Disable an agent when:
- You don't have the use case (e.g., a B2C-only org may not need the Sales Assistant)
- You're worried about overlap with a real human role and want to introduce the agent gradually
- You want to evaluate one agent at a time before opening the catalog wider
Re-enabling is a one-click reversal, so it's safe to disable speculatively.
Defaults
By default, all four catalog agents are enabled for every new workspace. Members see all four cards on /agentforce until an admin disables some.
Per-org isolation
Enable/disable state is per workspace. If you're an admin in two workspaces, your settings in one don't affect the other.
Custom agents (roadmap)
Custom agents — where you write your own role, instructions, and toolkit — aren't part of v1.0. The catalog model is the only path today.
If your team has a clear use case for a custom agent (e.g., a specialized internal-ops agent), let your account team know. Custom agents are on the roadmap.
Permissions
Only workspace admins can see and use the admin agents page. Members see the AgentForce hub and the chat surfaces but can't change which agents are enabled.
To delegate AgentForce administration, promote a teammate to admin from the workspace member list.
Audit
There's no built-in audit log for enable/disable changes in v1.0. If you need to know when a change was made, check the workspace activity feed. For workspaces with strict audit requirements, contact your account team.