> ## 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.

# NHI ownership assignment

> Continuously discover unowned non-human identities (NHIs) across your applications and automatically assign each one an owner, with a reviewer and fallback owner for the ones without enough correlatable signal to resolve confidently.

Every non-human identity (NHI) - service accounts, API keys, and similar credentials - should have a human owner accountable for it. Oleria continuously discovers NHIs across your connected applications and automatically assigns an owner (or more than one, when appropriate) to each, based on a combination of contextual signals. When there isn't enough correlatable signal to confidently resolve an owner, Oleria routes that NHI to a reviewer to resolve instead. This prevents orphaned NHIs from going unnoticed, reducing privilege sprawl, credential misuse, and audit failures.

## Ownership dashboard

Go to **NHI** → **Ownership** for a workspace-wide view of ownership coverage: total NHIs, owned NHIs, orphaned NHIs, dormant orphaned NHIs, and high-privileged orphaned NHIs. Below that, each connected application shows its own breakdown - total, owned, and orphaned NHIs - with a **Manage ownership** link to configure that application.

## How Oleria assigns owners

Oleria recommends an owner (or owners) for each NHI based on a combination of contextual signals - for example, the source system's recorded owner, who created it, a matching user name, or application-specific signals like admin status or group and role ownership. NHIs Oleria can confidently resolve this way are assigned automatically, with no review needed. See [how Oleria assigns NHI ownership](https://docs.oleria.com/posture/nhi-ownership-assignment-logic.md) for the full list of signals and the priority order Oleria checks them in.

When there isn't enough correlatable signal to confidently recommend an owner, the NHI goes to a reviewer to resolve manually instead. If you've enabled fallback assignment and the reviewer doesn't act in time, it's assigned to your configured fallback owner automatically.

## Configure ownership for an application

Select **Manage ownership** on an application from the Ownership dashboard to open its settings.

**1. Enable fallback assignment**

Turn on **Enable fallback assignment** so NHIs with no matched owner are automatically assigned based on the fallback owner you configure, instead of staying unowned.

**2. Set the fallback timer**

Under **Activate fallback after**, enter the number of days reviewers have to act on an ownership request before it's automatically assigned to the fallback owner.

**3. Choose fallback owners**

Under **Fallback owners**, assign a specific owner, or an admin, group, or role, to take ownership of NHIs that have no matched owner once the fallback timer expires.

**4. Choose reviewers**

Under **Reviewers**, assign who resolves the NHIs without enough correlatable signal to confidently assign an owner - a specific reviewer, or an admin, group, or role. If a reviewer doesn't act within the fallback window, ownership is assigned to the fallback owner instead.

**5. Set notifications**

Under **Notify assigned owners**, choose how owners are notified of new ownership assignments - email, Slack, or Microsoft Teams. Set up messaging in your workspace first if you want to notify by Slack or Teams.

> [!NOTE]
>
> Ownership settings are configured per application. Set them up for each connected application you want Oleria to assign NHI owners for.

## 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.