> For the complete documentation index, see [llms.txt](https://help.cerby.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.cerby.com/setup-and-admin/vault-management/create-a-vault.md).
# Create a vault
This article describes how to create a new vault for your workspace.
{% hint style="info" %}
**Who can use this feature?**
* Workspace **Owners**, **Super Admins**, and **Admins**
* Only supported using the Cerby web app
* The Cerby web app you are using must be added as a trusted device. For instructions, read the article [Set up trusted sessions on your devices](https://help.cerby.com/cerby-web-app/access/set-up-trusted-sessions-on-your-devices)
* If you are interested in this feature but don't see it available in your workspace, contact your Customer Success representative
{% endhint %}
As a workspace **Owner**, **Super Admin**, or **Admin**, you can create local or cloud vaults for your workspace.
To create a new vault, you must complete the following steps:
1. Log in to your [Cerby](https://app.cerby.com/) workspace using the Cerby web app.
2. Select the **Settings** option from the left menu. The **Workspace Configuration** page is displayed.
3. Select the **Privacy and security** left tab.
4. Scroll down to the **Vault management** section. A table with a list of vaults is displayed, as shown in **Figure 1**.
Figure 1. Table with a list of vaults in the Vault management section of the Privacy and security tab
5. Click the **Create new vault** button. The **Create new vault** dialog box is displayed.
6. Enter the vault name in the **Vault name** field. The name can be up to 50 characters long.
7. Select the corresponding option from the **Strategy** drop-down list:
* **Local vault:** Users hold the encryption keys that are not accessible by Cerby. This option is selected by default.
* **Azure vault:** Azure securely manages the encryption keys. This option is unavailable when your workspace already has an Azure vault.
* **AWS KMS:** Connect your AWS KMS with Cerby. This option is only available when the AWS KMS integration is turned on for your workspace.
The vault is created with the strategy you select.
{% hint style="info" %}
**NOTE:** The remaining steps describe creating a local vault. When you select **Azure vault** or **AWS KMS**, the dialog box asks for the connection details of that provider and the button changes to **Next**. For those steps, read the article [Set up an Azure Key vault integration](https://help.cerby.com/setup-and-admin/vault-management/set-up-an-azure-key-vault-integration) or [Set up an AWS KMS vault integration](https://help.cerby.com/setup-and-admin/vault-management/set-up-an-aws-kms-vault-integration).
{% endhint %}
8. Select the corresponding option from the **Visibility** drop-down list:
* **Workspace:** Everyone in the workspace gets access to this vault. This option is selected by default.
* **User:** Each user has their own individual and unique vault. A user can only have one vault with this visibility. The option is also unavailable in workspaces that do not support user vaults, and when you select the **Azure vault** strategy.
The vault is created with the visibility you select.
9. Select the **Set as default vault** option if you want to set the new vault as the default when adding an item to Cerby.
10. Click the **Create vault** button. The dialog box closes and a success message is displayed.
Now you are done. You can start using your new vault for your accounts and secrets.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.cerby.com/setup-and-admin/vault-management/create-a-vault.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
