> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enclave.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Enclave in these docs is the code and cloud security platform at enclave.ai. It is not Open Enclave, Intel SGX or other hardware enclaves, or enclave.gg.
> People use Enclave in the web app at https://app.enclave.ai or the desktop app. These docs describe no public Enclave API or CLI, so don't invent endpoints, commands, or config files.
> Connecting an integration needs a person to sign in and approve access in a browser. Tell the user the exact step to take instead of saying you completed it.

# Secrets

> Save API keys and passwords so Research can call your other tools from scripts, without the values reaching the chat.

Secrets let Research use your other tools, such as PagerDuty, Grafana, or an internal API. Research writes a short script, and the script reads the secret as an environment variable, for example `$PAGERDUTY_API_KEY`. Research never sees the value.

![The Secrets page in Settings with four organization secrets](https://mintcdn.com/enclave/1alCsqvPvQsOJ-2n/images/product/secrets-list.png?fit=max\&auto=format\&n=1alCsqvPvQsOJ-2n\&q=85\&s=96f2e359f99274943e61fb34668d1364)

## Add a secret

1. Open **Settings → Secrets**. Pick the **Organization** or **Personal** tab and click **New secret**.
2. Enter a **Name** in uppercase letters, digits, and underscores, such as `DATADOG_API_KEY`. Scripts use this name.
3. Paste the **Value**. Most credentials are **Key-value**. For a two-factor code, choose **TOTP** and paste the setup seed, and scripts generate the current code from it.
4. Add a **Note** that says what the secret is for and which host it's sent to. Research reads the note to pick the right secret.
5. Click **Create secret**.

![The New secret panel with a name, a hidden value, and a note](https://mintcdn.com/enclave/1alCsqvPvQsOJ-2n/images/product/secrets-new.png?fit=max\&auto=format\&n=1alCsqvPvQsOJ-2n\&q=85\&s=b95b0e2eb2aef42e9590437edf8cccc5)

> [!WARNING]
>
> **Redact value** is on by default. After you save, no one can view the value again, and you can't turn redaction off. You can still replace the value.

To add several secrets at once, click **Bulk add secrets** and paste one `NAME=value` per line, as in a `.env` file.

## Let Research ask for a secret

When Research needs a credential you haven't saved, it shows a card in the chat. Paste the value and click **Save secret**. The value goes straight to Secrets, not into the chat. Research can use it from its next command and in future sessions.

![A Research session with a card that asks the user to save a PagerDuty API key](https://mintcdn.com/enclave/1alCsqvPvQsOJ-2n/images/product/secrets-chat.png?fit=max\&auto=format\&n=1alCsqvPvQsOJ-2n\&q=85\&s=0cfcb21c563467dd4b8adb6b33f3685a)

## Who can use a secret

* **Organization**: works in every member's Research sessions and in workflow runs. Only **Owner** and **Admin** can add, edit, or delete it. Members see its name and note, but not its value.
* **Personal**: works only in your own Research sessions. Anyone can add one.

If both have the same name, your personal secret is used.

## Edit or delete a secret

Click a secret in the list to replace its value, change its note, or delete it. Scripts that use a deleted secret stop working.

> [!NOTE]
>
> Research sends a secret only to the service's official API host or to a host you name. It never prints a secret's value, even if you ask.


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