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

# Secrets

> Store named tokens for BotGauge agent connections. Reference secrets as $NAME in headers, replace values safely, and see what uses each secret before deleting.

Secrets are named tokens that the agent connections in a project use. A secret belongs to one project, and other projects can't see it. BotGauge stores the value encrypted and never shows it again, so the Secrets table lists only the name, when it was added, and what uses it.

![The Project Secrets table with name, added date, and used by columns](https://mintcdn.com/botguage/CvMAYy1jOk7D5CuB/images/platform/project-secrets.jpg?fit=max\&auto=format\&n=CvMAYy1jOk7D5CuB\&q=85\&s=f0f98a197daa0eb4ba67e7a4dd548f95)

Project, Secrets. Values are never shown.

## Add a secret

A workspace Member or Admin opens **Project, Secrets**, chooses **Add secret**, enters a name and a value, and saves.

| Field | Rules |
| - | - |
| Name | Letters A-Z, digits 0-9, and `_`. For example `ZENDESK_TOKEN`. Names with spaces or other characters are rejected. |
| Value | Required, up to 8192 characters. |

Saving with a name that already exists replaces that secret's value.

## Use a secret

Reference a secret in a connection's headers by name, for example `Bearer $ZENDESK_TOKEN`. For a secret named `REFUND_TOKEN`, the header value is `$REFUND_TOKEN`.

## Update a value

Choose **Update value** on a secret's row, paste the new value, and save. The name stays the same. Everything that uses `$NAME` picks up the new value on its next run.

## See what uses a secret

The **Used by** column lists each connection or guardrail provider that references the secret. It is empty when nothing uses the secret.

## Delete a secret

Choose **Delete** on a secret's row and confirm. BotGauge refuses to delete a secret that something still uses, and it tells you which connections or guardrail providers reference it, so you know what to change first.

## Permissions

The Secrets settings screen is shown to workspace Members and Admins, and those roles can add, update, and delete secrets. The list endpoint itself is open to anyone in the workspace, and it returns only names and usage, never values.

Store a secret for your agentOpen [BotGauge](https://cloud.botgauge.com) to add a secret and use it in an agent connection.

[Try BotGauge →](https://cloud.botgauge.com)


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