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

# Secrets

> Store credentials for actions and integrations without placing them in prompts.

Use **Settings → Secrets** to store encrypted values that actions, MCP servers, and integrations need.

<Frame caption="Secret Manager keeps values write-only while showing provider, environment, scope, consumers, and update history.">
  <img src="https://mintcdn.com/persistence-ai/vTPO-R7syJyo2N_1/images/dashboard/settings-secrets.png?fit=max&auto=format&n=vTPO-R7syJyo2N_1&q=85&s=b1fe004a27103b40c11ea78bc52bb256" alt="Persistence Secrets settings with masked values and usage metadata" width="640" height="360" data-path="images/dashboard/settings-secrets.png" />
</Frame>

## Create and use a secret

<Steps>
  <Step title="Choose a stable name">
    Create a name that describes the credential, such as `CRM_API_TOKEN`. Avoid names that reveal the secret value.
  </Step>

  <Step title="Store the value">
    Enter the credential in Secret Manager. Do not place the same value in an agent prompt, test variable, or documentation.
  </Step>

  <Step title="Reference the secret">
    In a supported credential, header, or parameter field, insert the secret using the `{{secrets.NAME}}` form shown by the editor.
  </Step>

  <Step title="Test the consumer">
    Run a simulated call that invokes the action or integration and confirm both success and failure behavior.
  </Step>
</Steps>

## Rotate a secret

Update the stored value, test each dependent workflow, and revoke the old credential at its provider. Deleting a secret can immediately break every tool or integration that references it.