Skip to main content
Console administrators can see and do everything in the agents area. Everyone else needs agent permissions, which you assign to users and groups. On top of those permissions, Console applies two rules that keep an agent from becoming a way around someone’s own access:
  • Every identity has an owner, and an agent runs as an identity. Only the owner of that identity, or an administrator, can make the agent run.
  • The list of outputs shows titles only. To open an output and read what the agent found, you have to hold the permissions its run had.

Assign agent permissions

Agent permissions are service permissions, so you assign them the same way as other role-based access control (RBAC) permissions for Console services.
1

Open the user or group

Go to Settings > Users or Groups and open the user or group you want to change.
2

Select the permissions

On the Service access tab, find the Agents section and select the permissions to grant. The section only shows when agents are turned on.
3

Save

Click Save. Users who belong to several groups get the permissions of all of them.
To create and run agents, a user needs both Can manage and run Agents and Can manage Agent identities. To assign these permissions with the Console API or CLI, use the ID as a Console permission on the PLATFORM resource type.
You can’t grant agent permissions to an identity. An agent can’t manage agents or identities, including its own.

Understand who can run and change an agent

You own the identities you create: the Acts for field of an identity names its owner. An identity can never hold more permissions than its owner, and an agent runs unattended with the permissions of its identity. So that nobody can borrow your access through an agent, some actions need you to own the agent’s identity as well as hold the permission. When you create an event-driven agent, the preview of matching audit log events also needs the Can access the Audit log permission.

Understand who can read an output

Console treats listing an output and opening it as two different things:
  • The list shows one line per output: its title, its type, the task and agent that produced it, when, and its status. It never shows what the agent found.
  • Opening an output shows the result itself, the trace of what the agent did and, for approvals and recommendations, its actions. The result can contain data the agent read with its identity’s permissions, such as topic configurations or records.
Console records the permissions an identity has when a run starts. To open the output of that run, you have to hold those permissions yourself, on the same resources, at the time you open it.

What you see in the list

What you can open

If your permissions change after a run, an output you could read before can show You no longer have access to this output. Ask an administrator to restore the permissions if you need to see it. To approve or reject an approval, you need Can manage and run Agents as well as being able to open it. Anyone who can open a recommendation can mark it as actioned or dismiss it.