Secrets
Encrypted key/value pairs for sensitive values.
Secrets live next to Variables on a project's Environment tab, and work the same way from a usage standpoint — key/value pairs exported as environment variables to every step of every workflow in the project.
The difference is storage and visibility: a secret's value is encrypted at rest (AES-256-GCM) and the UI always shows •••••••• for it — the real value is never shown again after you save it, in the list or when editing. Leaving the value blank while editing a secret keeps its current value unchanged.
Because the value is genuinely write-only in the UI, there's no way to "copy" an existing secret's value out of CID later — keep your own record of it if you'll need it elsewhere.
On a shared project, only owners and admins can add or change secrets. Running a workflow sends secret values to the computer running it, so owners, admins and members — who can run workflows — can get them; viewers never do.
Something missing or wrong here? Let us know