Skip to main content
Vaults are app-scoped containers for secrets. Each Vault holds a collection of named secrets and a membership list that controls who can read, write, or rotate them.
Vaults (dark)Vaults (light)

Vaults — Forge Console at /platform/vaults

What you can do

  • Open a Vault you are a member of, and read its secrets’ names, types and rotation status.
  • Create and rotate secrets, as an Editor or Admin.
  • Manage members, as an Admin: give each person the Admin, Editor or Viewer role.
  • Delete a Vault or a secret, as an Admin.
Platform → Settings → Secrets. Vaults is the first of the Secrets tabs: Vaults · Connections · Instances · Mappings. The last three are Environments.

Vault list

The left panel lists all Vaults the caller is a member of. Click any Vault to open its detail panel.

Detail panel tabs

Secrets

Shows all secrets in the selected Vault with:
  • Name — the identifier used when referencing this secret in workflows or environment mappings
  • Type — sensitive (value never returned in plaintext) or variable (standard env var)
  • Status — rotation health: OK, Stale, or Rotation Required
  • Last Rotated — timestamp of the most recent rotation
Each initial value and rotated version is stored as a distinct managed secret through the active credential provider. Rotation preserves the Vault secret’s stable name and reference while creating a new version identity. Create and rotate requests are retry-safe; retrying an interrupted request continues the recorded operation instead of writing another version. Every stored version requires its own managed Secret identity and operation ID. Reveal, deploy, and auto-sync resolve the selected version through its recorded provider binding. An unavailable canonical binding fails safely; legacy Forge record locators are no longer read or stored. Deleting a Vault secret revokes every version in background steps and removes the Vault record only after every version has been processed.

Members

Shows the Vault’s access control list. Each member has one of three roles: The creator is automatically added as Admin.

Key state to watch

  • Stale and Rotation Required. The secret’s rotation health; rotate it before it is deployed again.
  • Sensitive values. A sensitive secret’s value is never returned in plaintext.
  • Membership. The list shows only Vaults you are a member of.
  • Environments — configure where Vault secrets are deployed