All docs
Feature reference Build tests 2 min reference

Secret value

A secret value is encrypted test data that Rima masks in the interface, logs, and run evidence.

This reference explains the term, its purpose, a practical example, common use cases, where it appears in Rima, and the closest product visual.
A Rima project detail page
Project settings, variables, groups, schedules, tests, and run history in one place.

Definition

A secret value is encrypted test data that Rima masks in the interface, logs, and run evidence.

What it is for

Use secrets for credentials or tokens that a test needs but people reviewing results should not see.

How it works

  • Mark a project variable or an editable step value as secret; Rima encrypts it and shows a masked placeholder everywhere.
  • Runs use the real value, but the interface, logs, and stored evidence stay masked.
  • Secret values are not sent back to the browser; leaving the value blank while editing keeps the existing secret.

Example

Save a password as a secret project variable and select it in the login password step; run output shows a masked value.

Common use cases

  • Passwords.
  • API tokens.
  • Private customer identifiers.
  • Sensitive form data.

Where to find it

Mark a project variable or editable step value as secret in the project test editor.

Limitations, requirements, and permissions

  • Once saved as secret, the value cannot be read back from the interface; re-enter it to change it.
  • Anyone with test-edit permission can point steps at a secret, so scope project access accordingly.

Related features and guides

Ready to try it yourself?

Create your free account, record your first flow, add a validation, and let Rima run it on a schedule for you.

Start free trial