Introduction

A sweep does not put anything under governance. It produces a list of discovered assets on the connection that found them, and leaves them there until somebody decides which ones matter.

Registering is that decision. It is a deliberate, reversible act, and it is what moves an asset from "we know this exists" to "this is governed".

"Discovery answers what exists. Registration answers what we are accountable for. They are not the same list, and they should not be."

Where to find it

AI Governance > Discovery > select a connection > Assets

Access to AI Governance is granted through platform roles. Ask your workspace administrator, or see Settings > Governance > Roles for how permissions are assigned.

The Assets table

Opening a connection shows everything it discovered — "agents and models discovered and registered through this connection", with a count beside the heading.

What the statuses mean here

1. Excluded — Discovered, not registered. Its REGISTER toggle is off, and nothing governs it. This is the default state of everything a sweep returns.

2. Setup Pending — Registered, but no traces have arrived yet. Open the agent's Setup tab to instrument it.

3. Active — Registered and reporting.

Register discovered assets

Step 1: Open the connection

From Discovery, click the connection you want to work through. If the sweep is still running you will see Initial sync in progress — wait for it to finish.

Step 2: Decide what to register

Read the list before you act on it. Three outcomes, and most assets are one of the first two.

1. Register it — It handles company data or talks to customers. Toggle REGISTER on.

2. Leave it discovered — It is real but low-risk. Leaving it Excluded is a decision, and a defensible one — you know it exists and have chosen not to govern it.

3. Retire it — Nobody claims it and it has not run in months. Retire it on the source platform; the registry reflects the platform, so a toggle here does not stop the agent.

Step 3: Register, one at a time or all at once

Toggle REGISTER on individual rows, or use the N assets discovered banner's Register All to take everything the sweep returned. Dismiss hides the banner without registering anything.

Register All is the right move on a platform you already understand. On a first sweep it skips the review step that makes the inventory worth having.

Step 4: Assign ownership

Ownership is the step people skip and regret. Incidents route to owners; an unowned agent generates findings nobody triages, which is worse than no finding at all.

Step 5: Apply a policy

Registration brings an asset into the registry. It does not put it under policy — that is applied separately. See Apply a Policy to Assets.

Registering automatically

A connection's Settings carries Auto-register agents — "add newly discovered agents to the registry automatically". It is off by default.

Turned on, every agent a future sweep finds is registered without review. That is the right setting once you know what a platform holds and you want new agents governed from the moment they appear. It is the wrong setting on a platform you have not yet inventoried, because it converts a review queue into a registry you did not curate.

Refer: Sync interval and auto-register are set per connection. See Add an Application.

Important considerations

1. Registration is per asset, discovery is per connection — The connection decides what is visible. You decide what is governed.

2. Governance tier is inherited, not chosen per asset — A registered asset carries its connection's tier. To govern two sets of agents differently, put them behind different connections. See Connection Type & Control Mode.

3. New assets keep arriving — Connected platforms are swept on their schedule, so this is a recurring review rather than a one-off migration.

4. Unregistering does not delete history — Toggling REGISTER off stops governing the asset. It does not remove the traces or incidents already recorded against it.