> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/system-management/settings/secrets.md).
# Secrets
To interact programmatically with DoControl, you can create secrets to safely store API keys of any integrated API or app in AWS Key Management Service (KMS). These secret keys can be safely used in your [HTTP action ](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/utilities.md#http-request)workflows.
{% hint style="warning" %}
You need **Admin** permission to create and edit secrets.
{% endhint %}
{% hint style="success" %}
Secrets are securely stored using [AWS Key Management Service (AWS KMS)](https://aws.amazon.com/kms/).
{% endhint %}
## Create secrets
You can add up to 20 secrets as API keys that are stored in AWS Key Management Service (KMS).
1. From the top-right corner in any screen, click **Settings** > **Workflows** > **Secrets**.
2. Click **Add secret**.
3. Enter the secret name. This name will be referenced from your workflows.
4. Enter the secret value**.** This is the API key that will be retrieved when the secret name is referenced.
5. Click **Save**.
{% hint style="warning" %}
After saving the secret, the value (API key) will not be accessible.
{% endhint %}
## Edit secrets
You can edit or remove secrets. To update a secret, remove it and recreate.
1. From the top-right corner in any screen, click **Settings** > **Workflows** > **Secrets**.
2. In the relevant row of the secret you want to update, click the **Delete** icon.
3. Click **Add secret** to recreate the secret with the updated settings.
---
# 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.docontrol.io/docontrol-user-guide/system-management/settings/secrets.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.
icon.
3. Click **Add secret** to recreate the secret with the updated settings.
---
# 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.docontrol.io/docontrol-user-guide/system-management/settings/secrets.md?ask=