Skip to main content
Beta: This requires the Agents beta.
An Agent needs both Tool access and Delegation, set on its page in Agents. Both start empty.

Tool access

An Agent can use a tool only when both of these allow it:
  • the person it acts for: their own policies and the tools they’ve turned on in Home. A tool they turn off is off for Agents too;
  • the Agent’s groups: the policies linked to the groups it’s in.
Add the Agent to groups with Add to groups, or from Groups & Policies. Only policies linked to its groups grant an Agent tools. Review access shows what they allow. Agents use remote tools; prompts, resources, MCP Apps, local tools and Conduit administration stay with people’s own assistants.

Delegation

Delegation is who the Agent may act for: Nobody, Everyone, including people who join later, or Selected groups and people. It grants no tools. For a selection, choose Edit selection, then Save selection. Check access shows whether the Agent may act for one person, and which tools it could use for them. An Agent acts for someone only through a sign-in the workspace would accept from them directly; see the people an Agent acts for. To stop an Agent acting for someone, remove them or their group from its Delegation, or switch the Agent off.

Who can change what

Workspace admins manage Agents, their groups and Delegation, and can pause a sign-in provider’s Agent access or remove an Agent’s Okta app. Approving Agent access and an Agent’s Okta app takes a workspace owner (details). People choose their tools and connected accounts on Home. API clients can’t widen what an Agent can do; see API restrictions.