DreamLake

Organization and team vaults

In the Vault dashboard, use Save in to choose Personal, an organization, or a team before creating an entry. The selector lists organizations you belong to and teams where you are a direct member. Personal remains the default on your own profile.

Organization members can save and read organization entries. Team entries require both organization membership and direct team membership. Team visibility, organization ownership, and membership in a parent team do not by themselves grant access to team secrets. Manage membership through the existing organization and team settings.

Each scope has separate storage. Identically named organization and team entries remain independent. Changing the selector opens another vault; it does not move or share existing entries. Leaving the organization or team removes access on subsequent requests. Deleting an organization, team, or its namespace also removes access.

Shared vaults support entry creation, metadata listing, reading, replacement, retirement, restoration, and write-outcome recovery. Access keys, OTP generation, remote setup, host-credential bindings, and encryption-key administration remain personal-only. Existing CLI and SDK commands continue to use the personal vault by default.

The API selects a shared scope with X-Vault-Scope: org:<organization-id> or X-Vault-Scope: team:<team-id> on every request. Authenticated account sessions can discover their available scope IDs and entry prefixes through GET /v1/vault/scopes. Omitting the header selects the personal vault. The server validates current membership rather than trusting the supplied scope or entry path.

Scoped management preview (not released)

Package B draft clients select the original immutable scope on every request: dl vault --scope team:<id> list, or client.vault.scoped("team:<id>"). Scope failures never retry against Personal. Recovery metadata is bound to the authenticated actor, scope and request ID. The dashboard clears the active scoped view when authority is lost and preserves metadata-only recovery IDs.

Organization OWNERs and direct-team OWNERs, ADMINs and MAINTAINERs can preview an explicit secret copy, commit destination resealing, recover its outcome, manage the export policy, and inspect redacted audits. Ordinary members retain entry CRUD. Personal OWNERs have the corresponding personal capabilities. GET /v1/vault/capabilities returns effective named actions and an authorization epoch.

Team scopes need current organization membership, so team guests have none. An archived team has no Vault scope until it is restored.

Copy requires an explicit destination scope, destination name, source revision and request ID. Preview never returns plaintext. Pending previews expire after 24 hours; committing rechecks both scopes, policy revision and source identity. Provider failures leave the source active and no destination; retrying a completed operation returns the original destination identity. Membership offboarding permanently cancels pending approvals, including after rejoining.

Final plaintext release and entry writes commit authority fences against the same actor and organization parents used by membership changes. Team authorization also requires direct membership. Secret values are resealed into the destination encryption context with a new entry identity; the source remains available and host bindings are not inherited.

Source-retiring moves return VAULT_CONSUMER_INVENTORY_REQUIRED: no complete immutable entry/scope consumer registry proves that all consumers were transferred. Destination customer-KMS boundaries return VAULT_DESTINATION_KMS_RESEAL_UNSUPPORTED; destination policy-aware provider selection and recovery are required before that path can be enabled. Shared OTP, KMS administration, access keys, host/machine credentials and delivery remain unsupported. These draft changes have not been deployed.