Update an agent's access control list
- Base URL
-
https://{kibana_url}
- PUT /api/agent_builder/agents/{id}/access_control
Replace the per-agent access-control entries. Each entry grants one user a role on this agent. Identify the user by their Kibana user profile uid (id). Entries created before profile uids were adopted may use name (deprecated) instead. The agent owner, cluster admins, and anyone access control grants Manager can call this endpoint. Each call replaces the entire entries list — the most recent successful update wins. To learn more about agents, refer to the agents documentation.
Required authorization
- Privileges agentBuilder:manageAgents
Request body
-
entriesobject · max items: 100required -
Access-control entries to apply to the agent. Each entry has a
type(for exampleuser), arole, and either anid(the principal user profile uid, preferred) or a deprecatedname(username). -
idstring · min length: 1 · max length: 1024 -
Stable identifier of the user to grant access to (Kibana user profile uid). Preferred over
name. -
namestring · min length: 1 · max length: 1024 -
Case-sensitive Kibana username of the user to grant access to. Still supported, but
idis preferred for new grants because a username cannot distinguish same-named users across authentication realms.
Responses
Indicates a successful response
Bad Request — the request body failed validation, or the request targets the built-in Elastic default agent (which cannot have custom access control).
Not Found — no agent with this ID is visible to the caller, or the caller lacks write access. Matches the existing agentNotFound shape so unprivileged callers cannot probe for hidden agents.