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

# Open the Vault

> Meet the two-factor requirements, unlock the Vault with an authenticator code once per session, and lock it again when you're done.

The Vault is protected by Two-Factor Authentication. Before you can view or change it, your organization and your account need to meet a few requirements. After that, you open the Vault once per session with a code from your authenticator app.

## Before you start

You can open the Vault only when **all** of the following are true. If something is missing, the Vault page shows **You cannot open the Vault yet**, tells you what is missing, and links to the setting you need.

**1. You are an organization admin**

Only admins can open the Vault. Members connect through Vault secrets from the **Connectors** page and never need to open the Vault.

**2. Two-Factor Authentication is on for the organization**

In **Settings** → **Security**, turn on **Allow Two-Factor Authentication** for your organization. While it is off, the Vault is read-only for everyone.

**3. You have set up an authenticator app**

In **Settings** → **Security**, select **Enable 2FA** and add DeepMask to an authenticator app on your phone. See [Two-factor authentication](https://documentation.deepmask.io/two-factor-authentication.md) for the full setup.

**4. Your session is recent enough**

Your current session must have passed a two-factor check and must have started **after** you set up the authenticator. If you just set up your authenticator, sign out and sign in again.

> [!NOTE]
>
> The sign-in requirement is intentional. It prevents someone who has stolen a session from adding their own authenticator and using it to open the Vault.

## Open the Vault

**1. Go to the Vault**

Open **Settings** and select **Vault**.

**2. Enter a code**

Select **Open Vault** and enter the current six-digit code from your authenticator app.

**3. Work in the Vault**

The Vault shows your secrets and stays open for this session for up to one hour. Changes you make while it is open don't ask for another code.

Only codes from your authenticator app open the Vault. Recovery codes, emailed codes, and "remember this device" don't work here. Each code can be used only once — if you see **This code was already used**, wait for the next code in your app.

## When the Vault closes

The Vault closes automatically at the earliest of these moments:

* One hour after you opened it.
* When your session ends — for example, when you sign out, sign in again, or your session is refreshed.
* When you select **Lock Vault**.

The Vault is open only in the session where you entered the code. Another browser or device signed in to the same account stays locked.

> [!TIP]
>
> Select **Lock Vault** when you finish your changes, especially on a shared computer.

### If the Vault closes while you work

DeepMask doesn't interrupt you when the Vault closes. You find out at your next action, which shows **The Vault was closed (it opens for up to an hour). Enter a code to open it again.**

* Changes you already saved are kept. Only the action you were trying is not applied.
* Enter a fresh code from your authenticator app to open the Vault again, then repeat that action.
* If you signed in again or your session was refreshed in the meantime, you also need a new code. The previous unlock belonged to the old session.

## Lockouts

If 10 wrong or already-used codes are entered within an hour, you are locked out of the Vault for one hour. This counts Vault unlock attempts and other admin approvals together.

While you are locked out:

* You can't open the Vault or apply any change, even in a session that was already open.
* Every admin in your organization receives an email about the lockout.
* The lockout ends by itself after an hour. There is no way to unlock it early from the app.

> [!WARNING]
>
> If you didn't enter the wrong codes yourself, someone may be trying to use your session. Sign out of all devices, tell your other admins, and contact [contact@deepmask.io](mailto:contact@deepmask.io).

## If you lose your phone

Losing your authenticator doesn't affect existing secrets or member connections. It only stops you from opening the Vault until you set up a new authenticator.

> [accordion] You have a recovery code
>
> 1. Sign in and open **Settings** → **Security**.
> 2. Turn off Two-Factor Authentication, entering a **recovery code** instead of an authenticator code.
> 3. Set up the authenticator again on your new phone, and store the new recovery codes.
> 4. Sign out and sign in again.
> 5. Open the Vault with a code from the new authenticator.

> [accordion] You have no recovery code
>
> Contact [contact@deepmask.io](mailto:contact@deepmask.io). For your security, nobody can open the Vault on your behalf. Support verifies your identity before resetting your Two-Factor Authentication. Meanwhile, other eligible admins in your organization can keep managing the Vault.

## Related pages

> [card] [Manage secrets](https://documentation.deepmask.io/vault/manage-secrets.md)
>
> Add, edit, replace, and remove Vault secrets.

> [card] [Vault security](https://documentation.deepmask.io/vault/security.md)
>
> How the Vault protects your organization's credentials.


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