Introduction
Three fields on an agent record answer "whose is this?" — and they answer three different questions. Owner is a person. Workspace is a boundary. Department is a label. Confusing them is the reason governance reports get sent to the wrong people.
Where to find it
AI Governance > Agent Registry > open an agent > Overview. The three sit together on the Agent Details card. All three are set at registration and cannot be edited on the agent afterwards.
The three fields
Field | Answers | Set where | Required |
| Who is accountable for this agent | At registration only | Yes |
| Which project the record lives in | Chosen in the | — |
| Which part of the business it serves | At registration only | No |
Owner
Owner is a person, picked from your platform's users. It is required at registration and prefilled with whoever is doing the registering — which is convenient and is also the field's main failure mode: accept the default and you have recorded the registrar, not the owner.
There is a second way an owner can be wrong without anyone touching it. Records created before an explicit owner field existed fall back to displaying whoever created the record. The card shows a name either way, so an inherited owner is indistinguishable from a chosen one at a glance.
Note: An unowned agent shows
Unassigned. That is a cleaner signal than an inherited name, because it is unambiguous. When you audit ownership, the rows worth the most scrutiny are not the blank ones — they are the ones naming someone who has never been asked.
What ownership is actually used for
Owner is not decoration and it is not access control — holding the Owner field grants nothing. It matters because three separate governance activities need a name and have nowhere else to get one:
Incident triage — An incident is assigned to a person. Deciding who that should be starts from who owns the agent.
Framework evidence — Every management standard in this space asks who is accountable for a given system. This field is the answer, or there isn't one.
Exclusion decisions — Choosing not to govern something is a risk acceptance, and risk acceptances belong to named people.
Workspace
Workspace is the project the record belongs to. It is not chosen on the agent — it follows from where the record was created — and it is a real boundary rather than a label: it governs who can see the record at all.
Two consequences show up in day-to-day use:
The
Workspacecolumn appears in the registry table only in the all-workspaces view, and only for users with global project read access. In a single workspace it would be the same value on every row.An agent that a colleague can see and you cannot is almost always a workspace boundary rather than a missing record.
Department
Department is an optional label drawn from the same list the rest of the platform uses for AI agent departments. Unlike Workspace it grants and restricts nothing — its whole value is grouping.
It earns its keep at reporting time. "Which department's agents produce the most incidents", or "what is Support's AI spend", are questions with no answer unless this field is populated consistently. Populate it at registration or accept that those questions stay unanswerable.
"Workspace decides who can see the agent. Department decides how you report on it. Owner decides who gets the call."
What registration asks for
The manual registration drawer asks for Platform, then Name and Description (both required), then Owner and Department. For platforms that need a connection, Name is replaced by Connection and Agent pickers.
Description is required, and worth writing properly. It is the only field that records what the agent does, and it is the first thing anyone reviewing the registry six months from now will want.
Keeping these fields honest
Drift | How it happens | What to do |
Owner is the registrar | The prefill was accepted | Check the owner before you click |
Owner has left | Nothing reassigns on departure | Fold owned-agent reviews into your offboarding checklist and record handovers outside the product |
Department empty | It is optional and easy to skip | Set it at registration — it cannot be added to the agent afterwards |