Documentation Index
Fetch the complete documentation index at: https://docs.phrony.com/llms.txt
Use this file to discover all available pages before exploring further.
Description
A secret is a named sensitive value (API key, token, etc.) stored securely for your workspace. Use Secret Manager when a model connection or integration needs credentials.
| Topic | What to know |
|---|
| Why use secrets | Reference them from providers and integrations so keys are not pasted into agent prompts or chat where they leak easily. |
| Runtime and agents | Secret values are used only for configured connections (model calls, outbound HTTP). They are not exposed to the agent as readable content during a run. |
| After you save | The dashboard shows names and metadata only, not the raw value again—by design, to limit accidental exposure. |
Where you can use secrets
You cannot paste a secret’s value into arbitrary fields. Supported wiring:
| Where | How it works |
|---|
| Secret pickers | On an LLM provider (API key secret) or an HTTP integration (Bearer / API key auth). You select the secret by name; the value is not shown. |
| HTTP placeholders | In HTTP integrations, supported text fields may use {{secrets.NAME}} where NAME matches the secret name (e.g. {{secrets.openai_production}}). Phrony substitutes the value when sending the request. |
Properties
| What you manage | Description |
|---|
| Name | A label you choose, unique in the workspace, so you can pick the right secret in dropdowns. |
| Kind | User: secrets you create in Secret Manager (choose this when adding your own keys). System: credentials Phrony stores when you connect some integrations; those do not appear in the Secret Manager list and are not edited here. |
| Value | Entered only when you create or rotate the secret. It is not shown again after you save. |
| What uses it | Shown indirectly: for example, which model connection or integration points at this secret. |
How to create, edit, and delete
Create: Sidebar → Secret Manager → Add Secret, or Quick Create → New Secret. Set Name, Kind → User, and Value → Save secret. System secrets from some integrations never appear in this list; see Kind above.
Change or rotate a value: Secrets are not editable in place. Add Secret with a new Name and Value → point LLM providers or integrations at the new secret → delete the old row when nothing references it.
Delete: Secret Manager → row ⋯ → Delete → confirm Delete secret? → Delete.
Notes
- Secrets you add yourself use Kind User. System credentials from integrations are not listed here.
- The table shows names and metadata, never the secret value again after save.
- Duplicate names are not allowed in the same workspace, so you can rely on clear labels.
- Plan your rotation (new secret → update links → remove old) instead of trying to “view” a stored value again in the UI.
Warnings
- Removing a secret that is still in use will break calls to LLM providers or integrations until you attach a new credential.
- People who can see secret names can infer which vendors or systems you connect to; limit membership to people who need that visibility.
- Never put secret values in agent prompts, tickets, or source control.
