> ## 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.

# 0.6.3 — the sign-in page and channel restriction policies (upcoming)

> What Veriqa 0.6.3 brings: a cancel button and layouts for the sign-in page, per-application page texts, channel restriction policies, one-tap email over IMAP.

<Note>
  This version is being prepared for release: nothing described here is in the published packages
  and image yet. The latest release is [0.6.1](/docs/releases/0.6#061).
</Note>

## The sign-in page

* **A cancel button**, on by default — see [Cancel button](/docs/guides/customization#cancel-button).
* **Channel button visibility and an "all channels at once" layout** — see
  [Channel button visibility](/docs/guides/customization#channel-button-visibility) and
  [Channel layout](/docs/guides/customization#channel-layout).
* **Your own page texts for one application** — the `AuthPage.Texts` dictionary covers the sign-in
  page, the hop pages and the Email pages; see
  [Rewording a page element for one application](/docs/guides/customization#rewording-a-page-element-for-one-application).
* If resubscribing after a reconnect fails, the page falls back to polling the status; an expired
  sign-in stops the spinner on every page.

## Channel restriction policies

Anyone with a messenger can confirm a sign-in. Policies narrow that circle by what the channel
reports about the person confirming: only corporate email domains, only phone numbers from the
countries you name, or only users whose channel passes a phone number. They are set per channel in
configuration and are off by default. This is a filter on channel data, not a cryptographic barrier:
a country code is a number prefix, not where the person is. The keys are `RestrictionPolicy.*` in
the [key catalog](/docs/reference/configuration#keys-in-the-declaration-catalog).

## Channels

* **Email: one-tap email over IMAP** — no inbound mail provider and no public address needed, with
  mailbox sign-in by password or OAuth 2.0; see
  [One-tap email over IMAP](/docs/guides/channels#one-tap-email-over-imap).
* **An action after sign-in** — `CompletionBehavior`: a welcome message and a post-action in the
  chat; see [Veriqa:CompletionBehavior](/docs/reference/configuration#veriqacompletionbehavior).
* The text that asks for the phone number is an ordinary message kind, `phone-number-request`, and
  is edited like any other channel message.
* MAX in webhook mode parses a shared contact correctly.

## Documentation

A new [Observability](/docs/guides/observability) page: metrics, traces, logs and health checks.

## What to check when you upgrade

* **The Cancel button appears on every sign-in page.** If you built your own through `CustomJsPath`,
  remove it — or turn the built-in one off.
* **Phone numbers are accepted in E.164 only.** A custom or HTTP adapter that reports a number in
  another form no longer passes it on. The rule is the public `E164PhoneNumber` in
  `Veriqa.Core.Contracts`.


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