> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.qa.army/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.qa.army/_mcp/server.

# Authenticated Journeys

> Prepare email, one-time-code, phone, and sign-in journeys without placing credentials in test steps.

> **Warning**
>
> Managed email, one-time-code, phone, and SMS testing are unavailable.

## Model the customer outcome

Keep the Test focused on what the customer must accomplish: receive a message,
use the expected code or link, and reach the correct signed-in state. Do not put
passwords, codes, inbox contents, or phone numbers directly in Test steps.

## Prepare safely

* Use accounts created only for testing.
* Give each account the minimum product permissions required.
* Keep recovery paths separate from routine sign-in coverage.
* Use synthetic data rather than real customer records.

Governed Web Test Account references can supply authorized credentials without
placing their values in Test steps. Managed email, one-time-code, phone, and SMS
testing remain separate unavailable capabilities.