> For the complete documentation index, see [llms.txt](https://docs.strongdm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.strongdm.com/admin/access/secret-stores/strongdm-vault.md).

# StrongDM Vault

{% hint style="info" %}
This feature is part of the Enterprise plan. If it is not enabled for your organization, please contact StrongDM at the [StrongDM Help Center](https://help.strongdm.com/hc/en-us).
{% endhint %}

{% hint style="info" %}
This page only explains the StrongDM Vault secret store. For information on using StrongDM Vault to manage secrets, rotate them, or entitle them to users, see the [StrongDM Vault](/admin/secrets.md) page.
{% endhint %}

For organizations that require centralized storage of their credentials, and do not already use a secret store provider, StrongDM Vault has a built-in secret store option. It can be configured as a secret store in StrongDM and then used as an option for credential location when configuring resources. It can store passwords, certificates, and keys, based on what is necessary for access to each type of resource. Those credentials are securely encrypted and can be updated or removed as needed.

Creating a new StrongDM Vault secret store is as simple as going to **Settings** > **Secrets Management** > **Secret Stores** in the Admin UI, clicking **Add secret store**, naming the new store, and choosing the **StrongDM Vault** type.

{% hint style="info" %}
To manage the credentials inside of a StrongDM Vault secret store, you must create and use one or more relevant secret engines. For more information on managing secrets with secret engines, see the [StrongDM Vault](/admin/secrets.md) main section.
{% endhint %}


---

# 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://docs.strongdm.com/admin/access/secret-stores/strongdm-vault.md?ask=<question>&goal=<user_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.