Secrets

Studio → Settings → Secrets stores encrypted key-value pairs your organization's tools and integrations need — an API key a custom Tool's header requires, a webhook signing secret, anything sensitive that shouldn't be pasted directly into a config field.

Creating a secret

A secret has a key (letters, numbers, underscores, hyphens, and dots only) and a value. Once saved, the value is encrypted and never shown again in full — only the key is visible afterward, the same one-time-reveal pattern as an API key.

Referencing a secret

Instead of pasting a secret's value directly into a field (a Tool header, for example), reference it by expression:

{{secret.YOUR_KEY_NAME}}

Elizon resolves the expression to the decrypted value at the moment it's actually needed — the raw value is never stored anywhere except the encrypted secret itself. This means rotating a secret's value updates every place that references it, instantly, without editing each one individually.

Scope

A secret is created at the organization level or scoped to one project, the same org-vs-project choice most Settings resources offer.