Which fields should I populate first across a large inventory?

Owner, then Workspace. Ownership makes incidents actionable; workspace makes reporting possible. Department is useful but rarely blocking.

Why is COST empty on an active agent?

Cost derives from traces. No traces, no cost.

Is Description used anywhere beyond display?

It is the human context on the detail panel — what someone reads when deciding whether an incident on this agent matters. Write it for that reader.

Introduction

Every governed agent is one record. This page lists what that record holds, where each value comes from, and which ones you can change — the reference to keep open when you are reconciling an inventory or deciding what to populate first.

Where to find it

AI Governance > Agent Registry — as columns in the table, and under Agent Details on an agent's Overview tab.

Identity

Field	Type	Source	Description
`Name`	String	Platform, or entered	The agent's name. Discovered agents inherit the platform's name; manually registered agents use what you typed. Not required to be unique.
`Description`	String	Entered	What the agent does. Required at manual registration. Shown under the agent name on the detail panel.
`Platform`	Enum	Platform, or selected	Where the agent runs — for example `Microsoft Copilot`, `Anthropic`, `Salesforce`. Set once, at creation.

Governance

Field	Type	Values	Description
`Status`	Enum	`Active` · `Setup Pending`	Whether the record is complete and ready to be governed.
`Connection type`	Enum	`Observe · Advisory` · `Control · Enforced`	The governance tier. Inherited from the connection for discovered agents, set at registration for manual ones. Rendered as a badge on the detail panel.
`Policies`	Integer	0 or more	How many policies apply to this agent. `0` means inventoried but not governed.
`Incidents`	Integer	0 or more	Governance incidents raised on this agent.

Ownership and placement

Field	Required	Description
`Owner`	Yes at manual registration	The person accountable for the agent. Defaults to whoever registers it. Where incidents route.
`Workspace`	No	The workspace the agent belongs to. Renders as `—` when unset.
`Department`	No	Organisational placement, for reporting and routing. Renders as `—` when unset.

Activity and cost

These are derived from telemetry. Nothing here is editable — an empty value means no data has arrived, not that a field was left blank.

Field	Unit	Description
`Last trace`	Relative time	When the agent last ran. A dash means no trace has been received.
`Activity`	Traces	Volume over the selected window, as `N traces`.
`Trace count`	Integer	The tile on the `Overview` tab, over the selected period.
`Total cost`	Currency	What the agent has spent over the selected period.
`Error rate`	Percentage	Share of traces that ended in error.
`Latency P90`	Duration	90th-percentile trace latency.

The Overview tab scopes these to a period picker, defaulting to Last 7 days. Two figures quoted from different windows are not comparable — check the picker before you cite one.

Incident summary on the agent

The Overview tab carries an Incidents block headed "Governance incidents raised on this agent", with counts for Total incidents, Critical, High, Medium and Low, and a View incidents ↗ link through to the full list.

Below it, a table of recent incidents with INCIDENT, SEVERITY, STATUS and DETECTED. Severity commonly renders as —; that is expected and explained in Severity & How It Is Assigned.

Known limitations

Names are not unique — Two agents can share a name. Use platform and owner to disambiguate, and do not key anything external on the name.
Platform is immutable — Set at creation. Changing it means re-registering and removing the original.
Connection type is not editable per agent — For discovered agents it follows the connection. See Connection Type & Control Mode.
Two registry columns are hidden by default — The hidden-columns control above the table shows the count and lets you restore them.

Agent Record Reference