> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oleria.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Quick definitions for the acronyms and Oleria-specific terms used throughout these docs.

Acronyms are expanded on first use on every page. This page is a single place to look one up without hunting for where it first appeared.

| Term | Definition |
| :- | :- |
| Access Bundle | A pairing of an employee population, defined by an attribute filter, with the applications, groups, and roles they should have - provisioned automatically through lifecycle workflows and kept current by adaptive recommendations based on what the population's peers hold and use. See [Access bundles](https://docs.oleria.com/governance/access-bundles-and-adaptive-recommendations.md). |
| Access Graph | A visual map of user-to-resource relationships, showing how an identity reaches a resource through the groups, roles, and permissions in between. See [Access Graph](https://docs.oleria.com/posture/access-graph-overview.md). |
| Access Inventory | A tabular view of every application, group, role, and resource across your connected applications, with usage and dormancy on every row. See [Access Inventory](https://docs.oleria.com/posture/access-inventory-overview.md). |
| Access Review | A time-boxed campaign where reviewers certify or revoke the access each employee holds. Also called a user access review (UAR) elsewhere in the industry. See [Access reviews](https://docs.oleria.com/governance/access-review.md). |
| Accountable owner | An owner who is an active person in your organization or a group with members. An owner doesn't count as accountable when it only created the agent, has left your organization, has a disabled account, is a person outside your organization, isn't a person, or is a group with no members. A creator that is also recorded as an owner counts like any other owner. See [Agents overview](https://docs.oleria.com/governance/agents-overview.md#key-terms). |
| Action Center | Where every remediation Oleria submits - disabling an account, revoking access, removing a group member - is tracked, whether it ran once or on a schedule. See [Action Center](https://docs.oleria.com/workspace/action-center.md). |
| Agent | A software actor that operates with some degree of autonomy on behalf of your organization or a user, and that a connected application holds a record of. See [Agents overview](https://docs.oleria.com/governance/agents-overview.md). |
| Agent identity | An account the agent runs as. An agent can run as several accounts, or have no account of its own. See [Agents overview](https://docs.oleria.com/governance/agents-overview.md#key-terms). |
| Autonomy level | How independently the source application says an agent acts - **Autonomous**, **Semi-Autonomous**, **Supervised**, or **Unavailable**. See [Agents inventory](https://docs.oleria.com/governance/agents-inventory.md#autonomy-level). |
| Composition | What an agent is built from - the models, tools, Model Context Protocol (MCP) servers, knowledge sources, and other objects it depends on. See [Agents overview](https://docs.oleria.com/governance/agents-overview.md#key-terms). |
| Controls | The guardrails and observers that apply to an agent. A guardrail can block what the agent receives, produces, or does. An observer records it and can't block it. See [Agents overview](https://docs.oleria.com/governance/agents-overview.md#key-terms). |
| Dormant Days | How long an account, resource, or group membership has gone without recorded activity. See [Dormant days](https://docs.oleria.com/governance/account-dormant-days.md). |
| Entitlement | A specific permission or access grant within an application - for example, a role, a group membership, or a resource-level permission. |
| Hosting model | Where an agent runs - **Embedded** (a feature of another vendor's application), **Local** (on an end-user device), **Platform Hosted** (on a vendor's agent platform you configure), **Self Hosted** (on infrastructure you operate), or **Unavailable**. See [Agents inventory](https://docs.oleria.com/governance/agents-inventory.md#hosting-model). |
| HRIS | HR information system - the system of record for employees, such as Workday, that Oleria uses for employee lifecycle events. |
| IGA | Identity governance and administration - the industry term for governing who has access to what. Oleria's version continuously enforces least privilege using activity, dormancy, and peer signals, instead of relying only on point-in-time reviews. See [Govern every identity](https://docs.oleria.com/introduction/overview.md#govern-every-identity). |
| ISPM | Identity security posture management - continuously mapping every identity, group, resource, and permission across your environment to find exposure. In Oleria, this is the access graph itself. See [Access Graph](https://docs.oleria.com/posture/access-graph-overview.md). |
| ITDR | Identity threat detection and response - answering who had access to what, how they got it, and what they did, to speed up incident investigation. See [Activity analysis](https://docs.oleria.com/posture/activity-analysis-overview.md). |
| JIT access | Just-in-time access - granting access for a limited, time-bound window instead of indefinitely. |
| JML | Joiner, mover, leaver - the three employee lifecycle events Oleria automates access for. See [Employee lifecycle](https://docs.oleria.com/governance/employee-lifecycle-overview.md). |
| Live version | A version of an agent that is currently live. Oleria lists live versions only. See [Agents overview](https://docs.oleria.com/governance/agents-overview.md#key-terms). |
| MCP | Model Context Protocol - a protocol that lets an AI agent connect to tools, data sources, and other servers. An agent can accept calls over MCP, or depend on an MCP server as part of its composition. See [Agents inventory](https://docs.oleria.com/governance/agents-inventory.md#protocols). |
| MFA | Multi-factor authentication - requiring more than one method to verify an identity at sign-in. |
| NHI | Non-human identity - a service account, OAuth application, system account, or the account an AI agent runs as. The API keys and tokens an NHI authenticates with are its [secrets](https://docs.oleria.com/posture/nhi-secrets-overview.md). See [NHI inventory](https://docs.oleria.com/posture/nhi-inventory-overview.md). |
| Orchestration role | An agent's position among other agents - **Coordinator** (delegates work to other agents and also acts itself), **Router** (only delegates work to other agents), **Worker** (another agent delegates work to it), **Standalone** (neither delegates nor is delegated to), or **Unavailable**. See [Agents inventory](https://docs.oleria.com/governance/agents-inventory.md#orchestration-role). |
| Principal | An account, group, or role. See [Agents overview](https://docs.oleria.com/governance/agents-overview.md#key-terms). |
| Privilege | Oleria's rating of how much access an account, or a specific piece of access, holds, based on its scopes and permissions - **Elevated**, **Standard**, **Limited**, **None**, or **Unknown**. For a non-human identity, it rolls up every access grant it holds. See [NHI privilege](https://docs.oleria.com/posture/nhi-privilege-overview.md) and [Agent details](https://docs.oleria.com/governance/agent-details.md#agent-identities). |
| Protocols | The protocols an agent accepts calls over - **A2A** (Agent2Agent), **AG-UI** (Agent User Interaction), **HTTP**, **MCP** (Model Context Protocol), **Unavailable**, or **None**. See [Agents inventory](https://docs.oleria.com/governance/agents-inventory.md#protocols). |
| Remediation | An automated or manual action that removes or restricts access - for example, disabling an account or removing a group member. |
| Risk level | The highest severity among an agent's risk reasons - **Critical**, **High**, **Moderate**, or **Low**. See [Agents overview](https://docs.oleria.com/governance/agents-overview.md#key-terms). |
| Risk Monitoring | Every security finding Oleria detects across connected applications, prioritized by severity, surfaced from **Authentication Hygiene**'s **Risks by severity** card (available when enabled for your workspace). See [Risk Monitoring](https://docs.oleria.com/posture/risk-monitoring-overview.md). |
| Risk reason | One specific condition that makes an agent risky, such as **Shares an account with other agents**. See [Agent risk](https://docs.oleria.com/governance/agent-risk.md). |
| SCIM | System for Cross-domain Identity Management - a standard protocol for automatically provisioning and deprovisioning user accounts and groups from an identity provider. |
| Secret | An API key, token, certificate, or password a non-human identity (NHI) uses to authenticate - what connects an NHI to the applications it can reach. See [Secrets inventory](https://docs.oleria.com/posture/nhi-secrets-overview.md). |
| Separation of Duties (SoD) | A control that keeps any one person from holding two jobs that should be split, such as creating an account and also making it an administrator. See [Separation of duties](https://docs.oleria.com/governance/separation-of-duties.md). |
| Shadow IT | Applications your users are accessing outside your approved software catalog, detected from OAuth app data in your connected identity providers and from sign-ins the Oleria browser extension reports. See [Shadow IT](https://docs.oleria.com/governance/application-hygiene-overview.md). |
| Source application | The connected application an agent was discovered in. Many values on the Agents pages are what the source application declares about the agent. See [Agents overview](https://docs.oleria.com/governance/agents-overview.md#key-terms). |
| SSO | Single sign-on - signing in to multiple applications through one identity provider. |
| View | A saved filter set that takes you straight to a specific slice of a page's data. See [Views](https://docs.oleria.com/workspace/views.md). |
| Workflow | An automated identity or access action with a trigger, a condition, and an optional approval step. See [Workflows](https://docs.oleria.com/posture/workflows-overview.md). |

## Contact us

For questions, contact us at [support@oleria.com](mailto:support@oleria.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.