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

> ## Agent Instructions
> Collabase documentation. Interface labels are quoted in English, as they appear in the product.
> Features marked Enterprise need the Collabase Enterprise Edition licence.

# Automation secret stores

> Connect HashiCorp Vault or Azure Key Vault so that connection secrets stay with you, and release a store to the workspaces that may use it.

With a secret store, a connection holds only a reference. Collabase reads the secret just before a step runs and does not keep it. Manage stores under **Administration, Secret stores**.

## Connect a store

**1. Choose the provider**

Select **Connect a store** and choose **HashiCorp Vault** or **Azure Key Vault**.

**2. Enter the details**

For HashiCorp Vault enter the address, the secrets engine, an optional namespace and a token, or an AppRole role ID and secret ID. For Azure Key Vault enter the vault address, tenant ID, client ID and client secret. Credentials are stored encrypted and never shown again.

**3. Allow a store in your own network**

Switch on **The store is in our own network** when the store has a private address. Loopback and cloud metadata addresses stay blocked in any case.

## Release a store to workspaces

A store is usable only in the workspaces you release it to. Select **Release** on the store and choose the workspaces. Connections of other workspaces cannot point to it.

## Remove a store

Removing a store works only while no connection points to it. The page says when connections still do.

## Related

* [Connections](https://collabase.ch/docs/automation/connections.md)
* [Automation OAuth apps](https://collabase.ch/docs/admin/automation-oauth-apps.md)


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