Skip to main content
Free plan, no cardStart free
Test data and credentials 7 min read Updated

Credentials vault: test logins your runs never see

The credentials vault keeps the test accounts your recordings and runs sign in with. A login typed during a recording is captured into it, or you add one by hand. Secrets are encrypted before they are stored, runs use them on the server without seeing the value, and only the owner can reveal one, after a fresh confirmation, with every reveal in the audit log. A teammate asks for time-boxed use of a private credential and the owner decides; the team owner has a break-glass path that is recorded and notified.

About this guide

Written for
QA leads and test managers · Security and compliance reviewers · SDETs and automation engineers

What goes in, and how

A credential arrives two ways: captured automatically during a recording session, and marked as such, or added by hand with a type, a label, the website, tags, an environment (detected from the website or pinned by you), a data classification, a rotation policy in days, an expiry date and notes. It is encrypted with AES-256-GCM before it is stored, always. Its visibility is Private (a teammate needs an approved grant) or Team (any teammate can use it in runs). The secret itself is never shown to anyone but you.

The vault is part of Solo Pro and above; on the Free plan it is the Credentials vault tool on the pricing page, with a limit on stored credentials that the page states when you reach it.

Using a credential in a run

Runs use the credential on the server and never see the secret. A bot identity carries a reference to a vault entry, not a password. The list shows when each credential was last used and flags the ones that need attention; a credential moved to the recycle bin stops working in runs at once.

Reveal, access requests and break-glass

  • Reveal is owner-only. A fresh identity confirmation unlocks reveals for a few minutes; a revealed value hides itself again after a short countdown, and every reveal is written to the audit log.
  • A member asks to use a private credential for a number of days, with a reason; the owner approves or denies it, with an optional note; a grant expires on its own.
  • The team owner can reveal a teammate's credential as an exception, not a right: a reason of at least ten characters is required and recorded, the owner is notified, and the event shows in the audit trail.
  • A platform operator sees the metadata of every credential in the organisation for lifecycle work, never the secret.

Rotate, retire and recover

Rotate stores a new secret and keeps the previous versions on the Versions tab. Moving a credential to the recycle bin stops it in runs immediately and keeps it restorable for 30 days; deleting it from the vault is final. The Activity tab and the audit log list reveals, grants, rotations and deletions, filtered by event or by credential.

Export and import

An export is sealed with a passphrase of at least 12 characters that you choose and the platform does not keep; the file is useless without it. An import re-encrypts every item under this workspace's key, marks it imported and skips duplicates by website and username, within your plan limit. Both need a fresh confirmation.

Who can do what

What each role may do with a credential in the vault
RoleOwn credentialsA teammate's credential
MemberEverything: use, reveal, rotate, grant, deleteUse a Team credential in runs; request time-boxed access to a private one
Team ownerEverythingEdit details; break-glass reveal with a recorded reason and a notice to the owner
Platform operatorNot applicableMetadata only, for lifecycle; never the secret

Questions people ask about this

Can support staff see my passwords?
No. A platform operator sees names, websites and dates for lifecycle work. The secret is revealed only to its owner, after a fresh confirmation, and the reveal is logged.
What happens to a run when I delete a credential?
The run stops using it at once. From the recycle bin it can be restored for 30 days; a deletion from the vault cannot be undone.
Why do I need a passphrase to export?
Because a backup is a file that travels. It is sealed with your passphrase and the platform does not keep a copy, so the file cannot be opened without you.

Source: /documentation/credentials-vault, updated 2026-11-16. Answers are checked against the shipped product on that date.

Found something out of date? The people who build the module answer the contact form on the home page, and corrections to this guide are dated above. Tell us.

This guide is about test data, the credentials vault and enterprise test-data management. Twenty tools, including ours, are compared by job.

Try it against your own app.

Record one flow and get four kinds of evidence back. Judge the results yourself.

  • Free plan, no card
  • 14-day Solo Pro trial
  • Demo replies within one business day
  • Data hosted in India