> ## Documentation Index
> Fetch the complete documentation index at: https://quashbugs.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Credentials

> Centralize test accounts and tokens so authenticated flows run without embedding secrets in prompts or tasks.

#### Why Credentials matter

Many test flows require the agent to be logged in — to a specific user account, an admin panel, or an authenticated API. Without credentials configured here, the agent reaches a login screen and stops. With credentials set up, it authenticates and continues.

#### Adding credentials

1. Click **+ Add Credentials** in the Credentials tab.
2. Give the credential set a clear name — e.g., `Standard User`, `Admin Account`, `Guest User`.
3. Fill in the fields:
   * **Username / Email**
   * **Password**
   * **API Key or Token** (if applicable)
4. Click **Save**.

Repeat for each credential set you need.

#### Multiple credential sets

You can store as many credential sets as your testing requires. Common setups include:

| Credential set          | Used for                                    |
| ----------------------- | ------------------------------------------- |
| Standard User           | Happy path flows — typical user experience  |
| Admin Account           | Admin panel testing, privileged actions     |
| Guest / Unverified User | Testing restricted access, onboarding flows |
| Staging credentials     | Tests against the staging environment       |
| Production read-only    | Smoke tests against production              |

When writing a task or recipe prompt, you can specify which credential set to use — e.g., *"Log in using the Admin Account credentials and verify the user management panel loads."* The agent pulls the stored credentials automatically.

> **Security note:** Credentials are stored securely and are never exposed in test reports, execution logs, or shared recipe views.