Platform capability

ARGENTOWNER OFFBOARDING

Book a demo

Master Control System · by Nyedis

01 / ARGENT CAPABILITY

People leave. Their agents keep working

An analyst builds three AI agents that summarize loan files for her team. On her last day HR switches her off. Her agents keep running on their own keys, and nobody asks who answers for them now.

  • Customer records keep flowing to an AI model on behalf of a person who no longer works there, and at audit time nobody can name the owner.
  • IBM found 92% of organizations with an AI-related breach lacked proper AI access controls.¹
  • Good practice already covers the person: NIST SP 800-53 control PS-4 says that upon termination an organization should "disable system access" and "retain access to organizational information and systems formerly controlled by terminated individual."² Agents are now part of what a leaver controlled.

Switching off the person is routine. Switching off their agents, without losing the work, is the gap.

02 / ARGENT CAPABILITY

The one idea: no active owner, no agent

Argent Strategic Intelligence sits between your AI agents and the models and tools they use. Every agent that works through Argent has a named human owner, and the gateway checks that owner on every request.

  • When the owner is switched off, by an admin in the console or by a connected directory, and Identity Governance is in enforce, the agent's very next request is refused. Nothing reaches the AI model.
  • The agents are not deleted. They and their keys are kept, so the work waits for a new owner instead of disappearing.
  • Argent decides from its own record of the person. The directory changes that record; Argent does not ask the directory on every request.
  • A new owner must be an active person in the same company account, placed in an organization or department. Anyone else is refused.
03 / ARGENT CAPABILITY

How it works, step by step

One thread, from the day someone leaves to the agents working again. The names are invented, as in the film.

  1. Rachel Hayes leaves the bank. Her loan team still sends work to the three AI agents she built.
  2. The directory removes her. The bank has connected Microsoft Entra under Identity sources. At its next check of the directory, Argent switches Rachel off, signs the change, and places a hold on the keys of the agents she owns.
  3. Her agents' next requests are refused. Each one is refused and nothing reaches the model.
  4. The Org chart shows it. Each of her agents reads "Refused at every request since Rachel Hayes left", with the number of requests refused in 24 hours, and the page header counts the agents without an active owner.
  5. An admin presses REASSIGN 3. Argent suggests a successor, in order: her department's admin, then her organization's admin, then her team. The admin confirms the first suggestion, Marcus Bell.
  6. One signed change. All three agents move to Marcus together, recorded before it takes effect. If any part is refused, nothing changes.
  7. The hold is released. Because the directory removed Rachel, a SuperAdmin releases the hold on her agents. The team's next request goes through, and Marcus answers for it.
04 / ARGENT CAPABILITY

What the operator sees

Three console pages show the leaver flow; a SuperAdmin releases a directory hold from the agent's own page.

ScreenWhat it shows
Identity sourcesThe connected directory, with Add connector, Connect, Test and Attribute mapping, and a status pill such as CONNECTED.
Person pageDisable and Enable for a person, with the agents they own.
Org chart header"3 without an active owner": the number of agents that have no active owner.
Org chart agent line"Refused at every request since Rachel Hayes left" and "N requests refused in 24h", counting only refusals caused by the owner.
Person statusDEACTIVATED with the reason: removed from the named directory, "Deactivated in the console", or "Deactivated by" an admin, "directory changes won't reactivate".
Reassign dialog"They are refused at every request until the new owner is active." A New owner picker grouped as SUCCESSION, EVERYONE ELSE and TENANT ADMINS, then REASSIGN.

After the change the dialog confirms it in names: "Marcus Bell now owns" the agent, "was Rachel Hayes".

05 / ARGENT CAPABILITY

Two ways out, both on the record

Not every exit starts in the directory. Both paths end the same way: refused agents and a signed record.

  • Directory leavers. Argent connects to Okta, Microsoft Entra, Auth0, Keycloak, LDAP directories and SQL databases (JDBC) and checks them in the background. A person removed there is switched off at the next check, and their agents' keys are held until a SuperAdmin releases them. Other identity providers and governance tools can push the change to Argent over SCIM instead.
  • Console disables. A SuperAdmin or TenantAdmin can disable a person on the Person page; department and organization admins can do it in their own branch with a passkey check. Once Identity Governance enforces, their agents are refused on the next request, and no directory sync can quietly undo it: only an admin's Enable does.
  • Signed before it takes effect. The disable, the directory deactivation and every reassign are signed events. If the record cannot be signed, the change is not made.
  • If the leaver also used the Argent console, that account ends too. A console account linked to a disabled person is refused on every request.
  • Ownership cannot be dropped by accident. A person who still owns agents cannot be deleted until those agents are reassigned or revoked.
  • Department admins can reassign their own team's agents one at a time, with a passkey check.
06 / ARGENT CAPABILITY

Where owner offboarding fits

Any team that has to show an exit really ended access, and that the work kept an owner.

07 / ARGENT CAPABILITY

How a team starts

Watch the owner check first, then enforce it when you are ready.

  1. Connect. Route your agents through Argent and connect your directory under Identity sources.
  2. Enforce. Read what the owner check would have refused in watch mode, then switch Identity Governance to enforce. From then on an agent whose owner was disabled in the console is refused on its next request. A directory leaver's agents are held as soon as the directory removes the person.
  3. Reassign. Hand each agent that lost its owner to an active, accountable person from the Org chart, with a signed record. Choose where Argent runs from the deployment options, and book a demo below to see it on your own use cases.
Argent Strategic Intelligence

Book a demo

See Argent Strategic Intelligence stop a real AI agent, live, with the engineers who built it.