Store and manage API keys, tokens, and secrets securely in CRHQ — encrypted at rest with AES-256-GCM.
Credentials are sensitive values — API keys, tokens, passwords — that agents need to access external services. CRHQ stores them securely and provides them to authorized agents on demand.
Go to Settings → Credentials to see all stored credentials. The list shows:
Actual secret values are never displayed in the UI after creation.
| Field | Description |
|---|---|
| Name | Descriptive label (e.g., "Slack Bot Token") |
| Service | Associated connector |
| Value | The secret (API key, token, etc.) |
| Environment | Production, staging, or development |
Credentials are protected by multiple layers:
Warning: Never paste credentials directly into a conversation. Always store them through Settings → Credentials and let agents access them through the proper credential system.
Click a credential to update its value (e.g., when rotating API keys). The old value is replaced immediately.
Remove credentials that are no longer needed. Ensure no active connectors depend on them first.