Skip to main content
Oleria discovers the AI agents in your connected applications. Security and identity teams use these pages to answer four questions: which agents exist, what each one can do, who can reach it, and which ones to fix first. An agent acts in your applications through the accounts it runs as, with whatever access those accounts hold. Some agents have no account of their own. They act with the access of whoever uses them, or through the credentials their tools run on. For those agents, the Agent Identities and Access tabs are empty, but the agent can still act. Who Can Use and Composition show who can use it and what it depends on, when Oleria holds that information.
Agent discovery is enabled per workspace. To turn it on, contact us at support@oleria.com. These pages describe a workspace where it is on.

What you can do

  • Keep one inventory of agents - list the agents from every connected application, with each agent’s type, lifecycle state, risk, owners, and the accounts it runs as.
  • See what an agent can reach - open an agent to see the access its accounts hold, down to the permissions and scopes.
  • See who can use an agent - list the accounts, groups, and roles allowed to use it, and whether the right is granted directly or inherited.
  • See what an agent is built from - the models, tools, Model Context Protocol (MCP) servers, knowledge sources, and other agents it depends on, and the guardrails and observers that apply to it.
  • Fix the riskiest agents first - each agent has a risk level, with the reasons listed.
  • Follow an agent on the Access Graph - agents, their versions, and credentials appear as nodes next to the accounts and resources they connect to.

What counts as an agent

An agent is a software actor that operates with some degree of autonomy on behalf of your organization or a user. Oleria lists an agent when a connected application holds a record of it. The Type column shows what kind of record that is, in the application’s own words. An agent is separate from the accounts it runs as. Oleria lists those accounts in their own right, and the agent’s page links to each one Oleria holds.

Where agents come from

Oleria discovers agents through these integrations: Oleria also discovers agents in other connected applications that have them, for example Box, ChatGPT, and Port.

Turn on agent discovery

1

Ask Oleria to enable it

Contact us at support@oleria.com and ask for agent discovery.
2

Connect an application that has agents

Connect one of the integrations above, if it isn’t connected already, by following its integration page.Reading agents can need permissions in the application that the integration didn’t need before. Each integration’s page lists the permissions that agent discovery uses.
3

Open the inventory

Go to Agents -> Inventory. In the classic navigation, open Access Inventory and select the Agents tab. Oleria reads an application’s agents each time its integration syncs.

Where to find agents

Key terms

Explore the Agents pages

Agents inventory

The summary tiles, columns, filters, and values of the list of agents.

Agent details

One agent’s accounts, access, users, composition, controls, and versions.

Agent risk

What each risk level and risk reason means, and what to check.

Read the Access Graph

How nodes and lines on the Access Graph read, including agents.

Contact us

For questions, contact us at support@oleria.com.