Navigation
Vault access. Public access is not open. This product is separate from initial Identity and Apparatus access.
Screenshots use fictional demonstration accounts. Your data and available actions may differ. Reviewed October 16, 2026.
Concepts
Understand lease attribution
A lease records who requested it, the workspace, the credential, the run and a justification. The authenticated identity is the authority; writing a different name in a reason does not change who performed the action.
Use one valid run identifier for related work and a concise reason that explains why access is needed. Avoid personal information or secret values in the reason. Browser copy actions also use the audited lifecycle; they are not an untracked bypass.
Inspect Activity on the credential or Activity & audit for the workspace. Expand an event to find technical attribution and correlation details. Human-readable account labels help browsing; stable identifiers support investigation when names change.
Attribution shows the interaction with Vault. It cannot prove that the consuming program used the value correctly or kept it out of logs. Verify that separately with a fictional credential before enabling a new agent integration.
Screen reference
