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

# Test inboxes and verification links

> How Mini receives sign-up emails, verification codes and magic links on @qa.minitap.ai addresses, and where your team can read them.

Every address on `@qa.minitap.ai` is a test inbox Mini can read during a run. Give a test account one of these addresses and Mini signs up, signs in, picks up the code or follows the verification link itself, with nothing for you to forward or paste. This page shows how to set one up and where you can read the same emails.

```text theme={"theme":{"light":"github-light","dark":"vesper"}}
pro-user@qa.minitap.ai
```

## Give a test account an inbox

Open the app, go to **Builds & test data → Test accounts**, and add or edit an account. In **Email address**, type a name before the `@` and keep the `qa.minitap.ai` domain.

| Your app signs in with | Fill in |
| - | - |
| An email code or a magic link | The `@qa.minitap.ai` address only. Leave **Password** empty. |
| Email and password, for an account in a given state (a paid plan, saved data) | The `@qa.minitap.ai` address and a **Password**. Create that account in your backend with the same address and password, then Mini reads any code the app sends it. |

You don't create the inbox anywhere: mail sent to any `@qa.minitap.ai` address reaches it. Leave **Email address** empty and Mini generates an address for you.

Pick a name no one else is likely to use, such as your company and the role: `acme-admin@qa.minitap.ai`. When another workspace already uses an address, Mini can't read its emails and the dashboard asks you to pick another one.

## Accounts that need no setup

* **New user**: this account comes with every app and Mini maintains it. It signs up from scratch on every run, with a fresh `@qa.minitap.ai` address, and reads the confirmation email or code from that inbox.
* **No account attached**: when a scenario has no test account and still hits a sign-up wall, Mini creates a throwaway `@qa.minitap.ai` identity, signs up and reads the code the same way.
* **Google sign-in**: the Google accounts **Shared by Minitap** are on `@qa.minitap.ai` too, and Mini reads their emails the same way.

## Read the emails yourself

You can see what arrived in a test inbox from two places in the dashboard. Both are read-only.

| Where | What you see |
| - | - |
| **Builds & test data → Test accounts → View emails** | The mail an account received since it was added, up to 7 days back. |
| The run report's **Emails** tab | The emails of that run. The ones Mini opened are marked **Mini read this**, and **Show in recording** jumps to the moment each one arrived. |

In the run's actions, inbox steps read like **Checked inbox**, **Got a sign-in code** or **Waited for a sign-in code, none arrived**, so you can tell when a code never came.

Emails can hold one-time codes, so they never appear on a run link you share outside the workspace.

## Limits

* **Only `@qa.minitap.ai` inboxes.** Mini can't read Gmail, Outlook or your company mailboxes. An account on your own domain needs a **Password**, or a phone number with a static code.
* **Email only.** For SMS codes, pin a static code for a test number in staging: see [phone number sign-in](https://www.minitap.ai/docs/minitest/setup/test-accounts.md#phone-number-sign-in).

## Next steps

> [card] [Test accounts and sign-in](https://www.minitap.ai/docs/minitest/setup/test-accounts.md)
>
> Every kind of sign-in, and how to attach accounts to scenarios.

> [card] [Read a run report](https://www.minitap.ai/docs/minitest/runs/run-report.md)
>
> The recording, the criteria and the emails of a run.

> [card] [What Mini can do](https://www.minitap.ai/docs/minitest/reference/capabilities.md)
>
> Sign-in, devices and browsers, at a glance.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.