Skip to main content
An asset inventory helps you identify what a workspace owns, who uses it, and what would be affected by a change. Start with resource IDs and dependencies rather than relying on names alone.
Manage resources through their existing product pages and APIs. There is no verified unified Assets library or generic asset-upload workflow. The resource-type enum alone does not establish support for every named asset category.

​
Build a useful inventory

Recording pending for a workspace resource inventory. No playable video is available yet.

Recording pending: review workspace resources and their dependencies. Follow the written guide below.

You need access to each resource you intend to review. Visibility in one list does not grant access to every related credential or file.
1

Record identity and purpose

Capture the resource type, ID, readable name, workspace, and responsible person. For agent behavior, keep the branch and version IDs too.
2

Review dependencies and access

Identify agents that reference a document, tool, or integration before changing it. Use sharing metadata where supported to review resource grants.
3

Use the resource-specific lifecycle

Follow the relevant update or deletion operation. Confirm the resulting record and review downstream references; removing one resource does not establish deletion of every exported copy.
No. Use the dedicated credential workflow and avoid including secret values in an inventory or export.
Catalog availability identifies a selectable offering. It does not by itself establish ownership or unrestricted redistribution rights.