Skip to main content
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.
The Vault is part of DeepMask Enterprise and is available to organization admins. Contact contact@deepmask.io if you don’t see Vault in your settings.

Why use the Vault

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.

Secrets stay secret

Secrets are write-only. After you save them, nobody can view them again — not admins, not members, not the API.

Decide who can use it

Make a credential available to everyone in the organization, or only to selected members and groups.

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

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

The admin adds a secret

The admin chooses a connector, enters its credentials, and decides who can use it. See Manage secrets.
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.
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

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

Open the Vault

Meet the two-factor requirements and unlock the Vault for your session.

Manage secrets

Add credentials, control access, and replace or remove them.

Connect with organization credentials

What members see when they connect through the Vault.

Vault security

Encryption, approvals, notifications, and lockouts.