Use case
The 'what is this system?' question, answered in one place
Asset records sit alongside credentials and runbooks under the same role-based access — so anyone with access to a system can see what it is, what it does, and who owns it.
System context lives where the access lives.
Assets, not just credentials
Record hosts, services, integrations, and ownership beside the secrets that reach them. Asset records inherit the same access controls.
Context that survives staff turnover
When someone leaves, the institutional knowledge about a system stays in the workspace — not in their head.
One workspace, one access model
Operators stop hopping between a vault, a CMDB, and a wiki. The system, its credentials, and its runbook are all here.