> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gloo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vaults

> App-scoped containers for secrets. Manage secret values, rotation schedules, and member access from the Vaults page.

**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 (light)](https://mintcdn.com/gloo-b243725a/Ndtg9NEpwGc2OULA/forge/images/console/platform/vaults-light.png?fit=max\&auto=format\&n=Ndtg9NEpwGc2OULA\&q=85\&s=f425b624cb36ac119c0e9ff150ac0631)

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.

## Navigating to Vaults

Platform → **Settings** → **Secrets**. Vaults is the first of the Secrets tabs: **Vaults** ·
**Connections** · **Instances** · **Mappings**. The last three are
[Environments](https://docs.gloo.com/forge/console/platform/environments.md).

## 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:

| Role | Capabilities |
| - | - |
| **Admin** | Manage members, manage secrets, delete the Vault |
| **Editor** | Create and rotate secrets, manage environment deployments |
| **Viewer** | Read secret names and rotation status (never plaintext values) |

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.

## Related

* [Environments](https://docs.gloo.com/forge/console/platform/environments.md) — configure where Vault secrets are deployed


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.