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

# Vault overview (Coming Soon)

> Store your organization's connector credentials once in the encrypted Vault and let members connect without ever seeing a client secret or API key.

The Vault is where your organization keeps the credentials its connectors need: OAuth app client IDs and secrets, shared API keys, and Custom MCP server keys. Admins add a credential once. Members then connect through it by choosing **Organisation connection** when they add a connector — they never see, copy, or type the secret themselves.

> [!NOTE]
>
> The Vault is part of DeepMask Enterprise and is available to organization admins. Contact [contact@deepmask.io](mailto:contact@deepmask.io) if you don't see **Vault** in your settings.

## Why use the Vault

> [card] Set up once
>
> Register the Salesforce or Microsoft app, or buy the Bright Data key, once. Every member who needs it connects in a few clicks.

> [card] Secrets stay secret
>
> Secrets are write-only. After you save them, nobody can view them again — not admins, not members, not the API.

> [card] Decide who can use it
>
> Make a credential available to everyone in the organization, or only to selected members and groups.

> [card] Every change is visible
>
> Each change is recorded in the Vault history, and every admin receives an email summary when a change is applied.

## What you can store

Each item in the Vault is called a **secret**. When you add one, you first choose its type.

| Type | Used for | What members do |
| - | - | - |
| **App credentials** | An OAuth app for Salesforce (Enterprise) or Microsoft (Enterprise) | Sign in with their own account. The organization's app is used for the sign-in, so each member still acts as themselves. |
| **App credentials** | An API key for Bright Data or 2slides | Connect without signing in. All members share the organization's key and act as one identity. |
| **App credentials** | A Custom MCP server URL plus an API key, or a consumer key and secret | Connect without signing in or entering a URL. The server URL is part of the secret, so the key can only be sent to the server you chose. |
| **Shared secret** | A set of key–value pairs that belongs to no connector | Nothing yet. Shared secrets are kept for upcoming workflows, automations, and agents. |

> [!NOTE]
>
> The Vault doesn't store OAuth 2.0 credentials for Custom MCP servers. Members connect to OAuth-protected Custom MCP servers with their own credentials, as described in [Custom MCP configuration](https://documentation.deepmask.io/connectors/custom-mcp.md).

## How it works

**1. An admin opens the Vault**

Admins open the Vault with a code from their authenticator app. It stays open for that session for up to an hour. See [Open the Vault](https://documentation.deepmask.io/vault/open-the-vault.md).

**2. The admin adds a secret**

The admin chooses a connector, enters its credentials, and decides who can use it. See [Manage secrets](https://documentation.deepmask.io/vault/manage-secrets.md).

**3. Members connect through it**

When a member adds that connector, DeepMask offers **Organisation connection** next to **My own credentials**. See [Connect with organization credentials](https://documentation.deepmask.io/vault/connect-with-organization-credentials.md).

**4. DeepMask uses the secret by reference**

The member's connector points to the Vault secret instead of holding a copy. Disabling, restricting, or deleting the secret takes effect at the member's next sign-in or token refresh.

## Who can do what

| Action | Admin | Member |
| - | - | - |
| Open the Vault and view the list of secrets | Yes, after passing the [requirements](https://documentation.deepmask.io/vault/open-the-vault.md#before-you-start) | No |
| Add, edit, replace, disable, or delete a secret | Yes | No |
| Choose who can use a secret | Yes | No |
| View a secret's value after saving | No | No |
| Connect a connector through a secret | Yes, if included in the secret's access list | Yes, if included in the secret's access list |
| Use their own credentials instead | Yes | Yes |

> [!TIP]
>
> Members always keep the choice. If a secret is available for a connector, DeepMask offers it as an option — it never forces members to use it.

## Next steps

> [card] [Open the Vault](https://documentation.deepmask.io/vault/open-the-vault.md)
>
> Meet the two-factor requirements and unlock the Vault for your session.

> [card] [Manage secrets](https://documentation.deepmask.io/vault/manage-secrets.md)
>
> Add credentials, control access, and replace or remove them.

> [card] [Connect with organization credentials](https://documentation.deepmask.io/vault/connect-with-organization-credentials.md)
>
> What members see when they connect through the Vault.

> [card] [Vault security](https://documentation.deepmask.io/vault/security.md)
>
> Encryption, approvals, notifications, and lockouts.


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