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

# Environment instances

> Add, edit, and delete vault environment instances: the Convex, GitHub, or Vercel deployment targets that vault secrets deploy to, and who may deploy to them.

**Instances** (`/platform/environments/instances`) lists the environment instances for a vault: the deployment targets that vault secrets are sent to. The page header reads **Environments** and the section **Vault Instances**. It is the **Instances** tab of the **Secrets** tab group, after **Vaults** and **Connections**; Secrets has no sidebar entry of its own and opens from the **Secrets** tab of **Settings** under **Platform**. Open it to add a deployment target for a vault or to grant someone deploy access to one.

![Environment instances (light)](https://mintcdn.com/gloo-b243725a/xyq5perq6SLByPBn/forge/images/console/platform/environment-instances-light.png?fit=max\&auto=format\&n=xyq5perq6SLByPBn\&q=85\&s=72bf351ea44f448dba7f451ea76c0034)

Environment instances — Forge Console at `/platform/environments/instances`

## What you can do

* Pick a vault in the filter (default **All Vaults**). The table appears only once a vault is selected; the choice is kept in the URL as `?vault=`.
* **+ Add Instance** opens the instance form, with the selected vault preselected.
* The row menu offers **Edit**, **Manage Members**, and **Delete**.
  * **Manage Members** sets who may deploy secrets to the instance. A mapping's **Deploy** button stays disabled for anyone who is not a member.
  * **Delete** asks for confirmation: secret mappings that target the instance stop deploying.

## Columns

| Column | Shows |
| - | - |
| **Name** | Instance name |
| **Platform** | **Convex**, **GitHub**, or **Vercel** |
| **Auto-Sync** | **On** or **Off** |
| **Created** | Creation date |

## Who can act

Viewing instances requires `environments:read`; **+ Add Instance** appears only with `environments:manage`.

> [!NOTE]
>
> Without `environments:read` the page says "environment\_instances:read permission required." The permission it checks is `environments:read`.

## Key state to watch

* "No instances for this Vault": the vault has no deployment target, so its secrets deploy nowhere.
* **Auto-Sync** **Off** on an instance you expect to stay current: confirm whether it should sync automatically, and use **Deploy** on Mappings in the meantime.
* Deleting an instance that mappings still target: those mappings stop deploying. Check [Mappings](https://docs.gloo.com/forge/console/platform/environment-mappings.md) first.
* A **Deploy** button disabled on Mappings with "Membership required": add the person through **Manage Members** here.

## Related surfaces

* [Vaults](https://docs.gloo.com/forge/console/platform/vaults)
* [Environments](https://docs.gloo.com/forge/console/platform/environments.md)
* [Mappings](https://docs.gloo.com/forge/console/platform/environment-mappings.md)


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