Skip to main content

Global Secrets

Global secrets are reusable sensitive values. They are useful when multiple agents or configured skills need the same credential, but they require careful scoping.

Open global secrets at https://your-deployment.example/app/data/secrets.

When to use a global secret​

Use a global secret when:

  • Multiple agents need the same service credential.
  • An organization wants a managed credential instead of per-user copies.
  • A system skill profile needs a shared value.
  • You want a single place to rotate a value.

Use an agent-scoped secret when only one agent needs the credential.

What to store​

Examples:

  • API keys.
  • Service tokens.
  • Environment-style configuration values.
  • Credentials required by a specific tool or system skill profile.

Do not store secrets as ordinary files or chat messages.

Admin checklist​

  • Use least-privilege credentials.
  • Keep production, staging, and local credentials separate.
  • Record the purpose of each secret in its name or description.
  • Rotate secrets when membership or vendor access changes.
  • Remove secrets that no longer have active assignments.
  • Avoid granting broad secrets to experimental agents.

For agent-level credential flows, see Secrets And Credentials.

Last updated on