Auth & Credentials
Store project login credentials for the QA agent to authenticate during tests
Credentials let the QA agent sign in to your application during test runs. They are project-scoped, so the same credentials are available across every environment in the project. They are not tied to a specific environment.
Adding credentials
- Open Environments & Auth.
- Switch to the Credentials tab.
- Click Add Credential and choose the credential type:
- Password for a standard username/email and password login.
- Google for a Google account used in Sign in with Google flows.
- Phone & OTP for a test phone number that logs in or signs up with a one-time code.
- Fill in the fields and save.
Credential fields
| Field | Required | Description |
|---|---|---|
| Label | Yes | A descriptive name like Admin User or Standard User. Must be unique within the project |
| Role | No | An optional role hint for the agent, like admin or editor |
| Username / Email | Yes | The login identifier for the account |
| Password | Yes | The account password |
For a Phone & OTP credential, the same two fields carry phone-specific values:
| Field | Required | Description |
|---|---|---|
| Phone Number | Yes | The test phone number, including country code, like +15551234567 |
| OTP Code | Yes | The fixed verification code that number always accepts, like 123456 |
The label is how the credential is shown in Login steps and @ mentions, and it must be unique within the project. You can rename it at any time: test steps and mentions reference the credential itself, not its label, so they keep working and start showing the new name.
Security
Credentials are encrypted at rest and only decrypted server-side, at run time, for the QA agent. Passwords are never shown again after entry. When editing, leave the password blank to keep the current value. Stored values never appear in plain text anywhere in the UI.
Using credentials in tests
There are three ways to use credentials in a test case:
- Login step — in a structured test, add a Login step and choose a credential from the dropdown. Put it at the start of the flow when the scenario should begin signed in as that account.
- Mention in step text — type
@in an Action or Verify step and pick a credential by label. For example:
Log in as @Admin User and open the members page
- Mention in an autonomous goal — type
@in the goal field and pick a credential the agent should use. For example:
Log in as @Standard User and confirm the dashboard shows the account name
The agent completes the login with the stored username and password. For Google credentials, it drives the Sign in with Google flow using the stored account. For Phone & OTP credentials, it enters the phone number, requests the code, and types the stored OTP.
Phone & OTP credentials
Phone login and signup flows normally depend on a real SMS, which a test run cannot receive. A Phone & OTP credential closes that gap: you register the number as a test account in your app or SMS provider, pin it to a fixed verification code, and store both here.
Set it up like this:
- In your app or SMS provider, configure the number as a test account whose verification code is always the same value. No real SMS is sent for it.
- Add a Phone & OTP credential with that number and its fixed code.
- Use it from a Login step or an
@mention like any other credential.
At run time the agent enters the phone number, triggers the code request, and submits the stored OTP. It never waits for an SMS to arrive and never asks you for a code, so a run is not blocked on message delivery. The same credential works for signup flows that verify a phone number.
Only use numbers configured as test accounts. If the number still requires a real SMS code, the stored OTP is rejected and the login step fails.
Because credentials belong to the project, Login steps and mentions work the same way no matter which environment the run targets.
Managing credentials
- Edit: open a credential from the Credentials tab. You can change the label, role, username, and password. Renaming does not break existing steps or mentions.