Digital assets are cloud and data resources: databases, storage buckets, APIs, data warehouses, ML models.
They can be created by hand, but they're usually discovered automatically by a cloud integration. Each record notes whether it was created manually, which integration imported it, and when it was last seen.
Only Name is required.
Optional fields:
Type - Database, Data lake, Cloud storage, API, Data warehouse, File system, Streaming platform, Message queue, Search index, Cache, ML model, Other.
Environment - Production, Staging, Development, Test, DR, Local, Other.
Status - Active (the default), Inactive, Maintenance, Deprecated, Archived.
Access level - defaults to Restricted.
Cloud provider, region, project ID, resource ID, console URL.
Description and physical location.
Compliance requirements, last audit date, next audit due.
Retention policy and retention period in days.
Digital assets are not checked out. Instead, each one has a custodian - either a person or a team who owns it.
Change the custodian from the detail page, or use the bulk owner change action from the list.
A digital asset that still has a custodian can't be deleted, either individually or as part of a bulk delete. Remove the custodian first, then delete it.
From the digital assets list you can change status, change the custodian, or delete in bulk.
Digital assets emit their own automation events: discovered, updated, removed, and became public. The last of these is worth wiring to a notification - see Automations.
