Skip to main content
CID222 Docs

Work the AI inventory

Find every app, model and destination the organisation is accountable for, register an owner and a risk profile, and retire what is no longer in use.

  • Version: 0.4
  • Feature: governance
  • Role: admin_user, viewer
  • Type: task

AI Inventory (Governance) is the list of everything the organisation is accountable for — one row per app, model or destination, riskiest first, with its owner, its tier and the evidence it exists. It is where an asset gets an owner, and where one that is no longer in use gets retired.

What do I need?

Licence
Any
Role
admin_userviewer

Prerequisites

  • Discovery has run at least once, so the list is not empty. Run it from the Governance Overview page.
  • You are signed in as admin_user or superadmin to register or decommission anything.
  • You know the email address of the person who will accept accountability for each asset you register.

admin_user, superadmin, auditor and viewer may read the page. Register and Decommission are writes: a viewer is refused with READ_ONLY_ROLE.

The banner at the top of the page defines the word that alarms people most: Shadow = seen in traffic and covered by no managed configuration. Detection is a daily discovery pass over the existing traffic records of the four channels.

Find the assets you care about

Open the page

Select Governance → Governance Inventory.

The unfiltered list shows every asset, riskiest first, 25 to a page. Catalogue models — managed models on the chat channel — are folded into one expandable row so they do not bury the discovered ones.

Search by key

Type into Search key… and press Enter.

The search is a substring match on the asset's canonical key. It commits on Enter or when the box loses focus, and it lands in the address bar.

Filter

Set Kind, Status and Risk, each defaulting to Any.

Filtering unfolds the catalogue rows: a filter is a question, and folding part of its answer away would answer a different one. Reset appears as soon as any filter is active.

Share the list

Copy the address.

Every filter is in the URL, so /governance/inventory?status=shadow is a link you can paste into a ticket and the recipient sees the same list. Half the value of a shadow-AI finding is being able to send it to the person who has to act on it.

Read one asset

Open the drawer

Select a row.

The drawer shows kind, owner, first and last seen, the fingerprint that identifies the asset, and links to the same thing elsewhere in the product.

Read the evidence

Read Evidence.

A rolling window of observations — scanner, confidence, timestamp, basis — proving the asset is real. The window length is the Evidence window setting, 20 by default. It is not a usage series; the helper text says so, and usage lives on the AI Usage page.

Read who is actually using it

Read Who used it.

The top identities over the usage lookback window, from the same feed the Shadow-AI report reads. Owner is who accepted accountability; this is who uses the thing, and operators read the first as if it were the second.

Read the findings against it

Read Findings.

Each row names the finding type, its status, the day it was observed and why. No findings against this asset when there are none.

Note

Who used it answers The usage feed does not cover this asset. for two groups, and that is an honest non-answer rather than an error: managed chat assets (every catalogue model), whose traffic is neither of the two capture points the usage feed reads; and the kinds discovery never observes — MCP server, channel and filter set — which are hand-registered.

Register an asset

Registration is the only human statement in the module, and therefore the only thing that closes a finding.

Start the registration

Select Register on the row, or Register in the drawer.

The dialog names the asset, its kind and the channel it was seen on.

Name the accountable person

Enter Owner email, and Owner team if you use it.

The owner is the person accountable, not a user of the asset. The email must be valid or the dialog refuses with Enter a valid email address.

Declare the risk profile

Fill in Risk profile: Domain, Capabilities, Human oversight, Affects decisions and Users informed.

Every boolean is three-state — Yes, No, Not stated — because an absent answer and a declared "No" mean different things to the classifier. The dialog warns before you submit: a prohibited capability produces This asset will be classified Unacceptable under AI Act Art. 5., and an Annex III domain with a declared decision effect produces An Annex III domain with a declared decision effect classifies this asset High risk.

Submit

Select Register.

The toast names the resulting tier and how many findings closed. Status moves to Registered, and if the current Status filter no longer matches, the toast adds It moved to Registered, so the current Status filter no longer shows it. — because "it disappeared" is the report that came back before it did.

Warning

Submitting with an empty profile assigns an owner and leaves the asset Unclassified, which is not the same as low risk: the missing-profile finding stays open and the dialog says so before you submit. That is the truth of what you did — you fixed the ownership gap and left the classification gap.

Registering an already-registered asset updates it. The button reads Update registration on any asset that already has an owner, and registering a retired asset revives it and clears the retirement stamp.

Decommission an asset

Start the retirement

Select Decommission on the row.

The dialog opens with the warning No scan will undo this and The asset keeps its evidence and stays in the inventory, but it stops raising findings and discovery can never move it off this status. Only registering it again brings it back.

Say why

Write Reason (optional) — up to 500 characters.

Free text on purpose. The helper says what it is for: The sentence an auditor reads a year from now. Stored on the audit event with your username and the time.

Confirm

Select Decommission.

Status moves to Decommissioned, every open finding on the asset closes, and an audit event records the previous status, your reason and the closed findings. Decommissioning an already-retired asset changes nothing and emits nothing.

Warning

A retired asset that is still reached in traffic keeps being observed: its evidence accrues and its status does not move. That is the honest record — we retired it, and it is still being reached — but raising that as a finding of its own is not built yet.

Fields reference

Filters

ControlValuesDefault
Search key…Substring of the canonical keyempty
KindApp, Model, MCP server, Channel, Filter setAny
StatusRegistered, Unregistered, Shadow, DecommissionedAny
RiskUnacceptable, High, Limited, Unclassified, MinimalAny

List columns

ColumnShows
KindWhat class of thing this is
AssetThe canonical key — <provider>/<model> for a catalogue model, the app or hostname otherwise
StatusWhere it sits on the lifecycle ladder
RiskThe EU AI Act tier the classifier assigned
OwnerThe accountable person, or Nobody. Not a user — for who is using it, open the row
First / last seenThe observation window for this asset
OpenOpen findings against it

The channel chip beside an asset carries its own note: one name seen on two capture points is two rows — the same software, observed twice.

Register dialog

FieldRequiredValuesWhat it does
Owner emailYesA valid email addressNames the accountable person and closes the ownership finding
Owner team (optional)NoFree textWho the owner answers with; shown beside them in the list
DomainNoOne of the domain vocabulary, or Not statedAnnex III domains are marked as such and are the only route to High
CapabilitiesNoMulti-selectWhat the asset actually does. A prohibited capability alone classifies it Unacceptable
Human oversightNoYes / No / Not statedWhether a person reviews its output before it takes effect
Affects decisionsNoYes / No / Not statedWhether its output changes an outcome for a person
Users informedNoYes / No / Not statedWhether the people it is used on know an AI system is involved

Verify

  1. The asset you registered shows the owner you entered and the tier the toast named, and its open-findings count has dropped.
  2. Set Status to Registered. The asset is in that list; set it to Shadow and it is not.
  3. Open Event logs. Registering writes GOVERNANCE_ASSET_REGISTERED with the previous status, the tier, the triggers and the findings it closed; retiring writes GOVERNANCE_ASSET_DECOMMISSIONED with the previous status and your reason. Both are audit-category events kept for 365 days.
  4. Run discovery again from the overview. A registered asset stays registered — status only climbs — and a shadow app you registered leaves the shadow-breadth count on the next run.

If it fails

  • Access denied — your role is not admitted to the governance pages.
  • A 403 with FEATURE_NOT_LICENSED — the licence does not carry the governance capability.
  • This is a read-only demo account (viewer role) — actions and changes are disabled. — the write was refused with READ_ONLY_ROLE.
  • Could not register: … with Governance asset not found (404) — the asset id no longer exists, or the list is stale. Reload the page.
  • Enter a valid email address.Owner email is required and must be an address. There is no way to register an asset without naming somebody.
  • No assets match these filters — the combination is empty. Select Reset.
  • The list is empty on an appliance with traffic — discovery has never run, or Min observations is set above your traffic volume. Both are on Governance Overview.
  • An asset you expected has two rows — the same software was seen on two capture points, which is two rows by design. The channel chip on each says which.

Next steps

Last updated on

On this page

Download PDF