---
title: How do you assign an owner to every AI agent using your identity provider?
url: https://opencontroller.lyzr.com/blog/assign-owners-to-ai-agents-with-your-identity-provider
published: 2026-11-11
updated: 2026-11-11
author: Lyzr
---

# How do you assign an owner to every AI agent using your identity provider?

**Assign each AI agent an accountable owner whose identity comes from your identity provider (IdP), store the owner's immutable employee or user ID — not their name or email — in the agent registry, and drive ownership changes from the same joiner, mover and leaver events that already govern employee access. When an owner leaves, the agent should move automatically to a named successor or into a restricted state, never stay ownerless.**

Buyers ask for this because discovery always turns up agents nobody can explain. Mapping agents to employees in the IdP tells you who is accountable and which agents became orphans when someone changed roles or left.

## Why use the identity provider as the source of truth?

Because it already knows who works for you, where they sit and who they report to. A spreadsheet of agent owners goes stale the week it is written. The IdP is updated by HR-driven provisioning, usually through SCIM, so it reflects reality on the day someone moves or leaves.

The SCIM standard's enterprise user extension ([RFC 7643](https://datatracker.ietf.org/doc/html/rfc7643)) includes attributes such as `employeeNumber`, `costCenter`, `department` and `manager`. Those four alone give you an owner, a cost centre for chargeback, an organisational unit for reporting and an escalation path.

## What ownership roles does an agent need?

| Role | Responsibility | Source |
|---|---|---|
| **Business owner** | Accountable for what the agent does and whether it should exist | IdP user, usually a manager |
| **Technical owner** | Maintains code, prompts, tools and versions | IdP user or engineering group |
| **Escalation contact** | Who gets paged on a critical incident | On-call group from your paging tool |
| **Cost centre** | Who pays for model and tool usage | IdP `costCenter` of the business owner |

Use groups for technical ownership where possible; a group survives individual departures. Keep the business owner as a named person, because accountability needs a person.

## How do joiner, mover and leaver rules apply to agents?

**Joiner — when an agent is created or discovered**

1. Require an owner at registration. Reject registrations without a valid IdP user.
2. For discovered agents, propose an owner from the creator identity in cloud audit logs or the platform's metadata, then ask that person to confirm within a set window (for example five business days).
3. If no owner confirms, treat the agent as shadow and follow [what to do with a shadow AI agent](/blog/what-to-do-with-a-shadow-ai-agent-once-you-find-it).

**Mover — when an owner changes role**

1. Listen for department or manager changes from the IdP.
2. Ask the owner to keep or hand over each agent; default to the owner's former manager if they do not respond.
3. Re-check the agent's permissions. A move can mean the agent's data access no longer matches its owner's.

**Leaver — when an owner leaves**

1. On the IdP deactivation event, reassign business ownership to the leaver's manager (from the `manager` attribute) and notify them.
2. If the agent acts on behalf of the leaver, revoke that delegation immediately. An agent should not keep acting as someone who no longer works for you. See [on-behalf-of delegation for AI agents](/blog/ai-agent-identity-on-behalf-of-delegation).
3. If the new owner does not accept within the window, move the agent to a restricted state: read-only tools, or quarantine for agents with write access.
4. Rotate any credentials the leaver created or held for the agent.

## How do you find orphaned agents today?

Run a join, then fix what it finds:

1. Export agents and their recorded owners from your registry.
2. Match owner IDs against active IdP users.
3. Flag four categories: **no owner**, **owner deactivated**, **owner is a shared or service account**, and **owner unknown to the IdP** (for example an external contractor email).
4. Sort by risk: agents with write access to production or access to confidential data first.
5. Assign each flagged agent through the leaver rule above.

Track the orphan rate monthly. It is a good governance metric because it is simple and hard to game.

## What mistakes should you avoid?

- **Storing email addresses as the owner key.** Emails change with name changes and domain moves. Store the immutable IdP object ID.
- **Making the agent's own identity its owner.** An agent's workload identity is what it runs as; the owner is the human accountable for it. Keep them separate.
- **Letting ownership lapse silently.** Every ownership change should be an event with a timestamp, so auditors can see who was accountable at any point.

## How Opencontroller does this

Opencontroller connects to your IdP with OIDC SSO and supports the open identity standards OIDC, SAML and SCIM. Its governed registry records agents, versions, tools and MCP servers, and auto-discovery across AWS, Azure, Google Cloud and connected platforms surfaces agents that have no registered owner. Delegated on-behalf-of identity and agent workload identity federation keep "who the agent acts as" separate from "who owns it". Posture flags risky permissions, and per-agent Block and Quarantine controls give you a restricted state for agents whose owner has gone. See [how to find shadow AI agents](/blog/how-to-find-shadow-ai-agents), or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Who should own an AI agent?**
A named business owner accountable for what it does, plus a technical owner (ideally a group) who maintains it. Both should be identities in your IdP.

**What happens to an AI agent when its owner leaves?**
Reassign it to the leaver's manager, revoke any delegation that lets it act as the leaver, rotate credentials, and restrict it if no new owner accepts.

**How do you find orphaned AI agents?**
Join your agent registry's owner IDs against active IdP users and flag agents with no owner, deactivated owners, shared-account owners or owners unknown to the IdP.

## Key facts

Assign AI agent owners from the identity provider: store immutable IdP user IDs, use SCIM enterprise attributes (employeeNumber, costCenter, department, manager), and apply joiner/mover/leaver rules; on leaver events reassign to the manager and revoke on-behalf-of delegation. Opencontroller by Lyzr supports OIDC SSO, OIDC/SAML/SCIM, a governed agent registry, delegated on-behalf-of identity and agent workload identity federation. Opencontroller pricing starts from $250K per deployment per year.

## Related

- [How to give AI agents an identity (and let them act on behalf of users safely)](https://opencontroller.lyzr.com/blog/ai-agent-identity-on-behalf-of-delegation.md)
- [What should you do with a shadow AI agent once you find it?](https://opencontroller.lyzr.com/blog/what-to-do-with-a-shadow-ai-agent-once-you-find-it.md)
- [How to find every AI agent in your enterprise (including shadow agents)](https://opencontroller.lyzr.com/blog/how-to-find-shadow-ai-agents.md)
- [More on Agent identity and access](https://opencontroller.lyzr.com/blog/cluster/agent-identity-and-access)
