Secrets

Secrets are org-level key-value pairs — passwords, tokens, connection strings — that your test steps can reference by name. At run time the runner substitutes each reference with its value; the value is never stored in the step definition or visible in run results.

Permissions

Members' tests can use secrets at run time. Admins and owners can view the secrets list, create, edit, and delete secrets. See Roles and permissions.

Add a Secret

1. Go to Operations → Secrets in the sidebar.
2. Click Add Secret.
3. Fill in the fields:

Names must follow environment variable naming rules (letters, digits, underscores; no spaces or special characters) because secrets are injected as environment variables at run time.

Edit a Secret

Click the edit icon on any row. You can update the Value and Description. The Name field is disabled — names cannot be changed after creation. Leave Value empty to keep the current value unchanged.

Delete a Secret

Click the delete icon on any row and confirm.

Reference a Secret in a Step

In the test step editor, input fields that support dynamic values accept a secret reference:

{{secrets.SECRET_NAME}}

Replace SECRET_NAME with the exact name of the secret as it appears on this page. The editor stores the secret key internally; the plaintext value is never saved to the step.

For example, to pass a login password to a Fill step, enter {{secrets.LOGIN_PASSWORD}} in the value field.

Next Steps

• Test Execution
• Email Inboxes
• API Keys
• Roles and Permissions