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

# Email

> Step-by-step screens for the Email channel: signing in on a computer and on a phone, and the claims your app can get.

## General scheme

A sign-in starts in your app: it sends the browser to the sign-in page with a standard OpenID Connect redirect. The user
confirms in a channel, and the browser returns to your app with a code that your app exchanges for tokens.

![Signing in through Veriqa: your app sends the browser to the sign-in page by an OpenID Connect redirect, the person confirms in a channel, and Veriqa redirects back so your app can exchange the code for tokens.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-flow-sign-in.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=ded6eede4a7e26ade7410dd12eb871de)

An action confirmation starts on your server: it creates a transaction through the Veriqa API. The user confirms in a
channel, and your server reads the answer and performs the action. The browser is not redirected.

![Confirming an action through Veriqa: your server creates the transaction, the person scans the QR code your app shows and confirms in a channel, and your server reads the answer and performs the action.](https://mintcdn.com/veriqa/XLg27VdhWjZL50TY/images/examples/en-flow-confirm.webp?fit=max\&auto=format\&n=XLg27VdhWjZL50TY\&q=85\&s=03bda77eac10a8b5d7423cfc53fc142b)

See [Basic scenarios](https://veriqa.app/docs/basic-scenarios.md).

## Signing in on a computer

![Signing in on a computer by email: QR code, phone camera, the user sends a ready-made email, the page verifies the sender, and the user confirms the sign-in on the computer.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-email-cross-device.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=f09bc7035c1c42fdb2ab4b59e4679914)

The user scans the QR code with their phone camera, sends the ready-made email and confirms the sign-in on the computer.

## Signing in on a phone

![Signing in on a phone by email: the user taps the email button and sends a ready-made email, the page verifies the sender, and the user confirms the sign-in.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-email-phone.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=454374ad99e15d2e71f36a3187836041)

The user taps "Send confirmation email", sends the ready-made email and taps Yes on the confirmation page.

## Claims your app can get

![Claims your app can get from signing in with Email: sub, amr, channel\_type, channel\_user\_id, name, email, email\_verified, preferred\_username, veriqa\_channel, veriqa\_email\_mode.](https://mintcdn.com/veriqa/ccCax_wh-JmrZJTK/images/examples/en-email-claims.webp?fit=max\&auto=format\&n=ccCax_wh-JmrZJTK\&q=85\&s=c30cefea728b445078e7e15514cdc24d)


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