> This page is for version V3 - Beta (default).
> For other versions, use one of these documentation indexes:
> - V3 - Beta (default): https://docs.authlyx.dev/v3/llms.txt
> - V2 - Legacy: https://docs.authlyx.dev/v2/llms.txt
> - V1 - End of support: https://docs.authlyx.dev/v1/llms.txt

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

# Release Channels

> Offer a test build to selected customers before the stable release.

Say your users have version `2.4.0`, and you want 12 testers to try `2.5.0-rc.1` first. Keep most identities on **Stable**. Move your test licenses to **Beta**. When they sign in, AuthlyX returns the latest release for the channel assigned to that identity.

```mermaid
%%{init: {"theme":"base","themeVariables":{"primaryColor":"#ffffff","primaryTextColor":"#171717","primaryBorderColor":"#404040","lineColor":"#606060","secondaryColor":"#f5f5f5","tertiaryColor":"#ffffff","edgeLabelBackground":"#ffffff"}}}%%
flowchart LR
  A[Developer publishes 2.5.0-rc.1 to Beta] --> B[Tester license is assigned to Beta]
  C[Customer license stays on Stable] --> D[Customer signs in]
  B --> E[Tester signs in]
  D --> F[AuthlyX returns Stable release details]
  E --> G[AuthlyX returns Beta release details]
  F --> H[App offers the Stable download]
  G --> I[App offers the test download]
```

The SDK reports the update details. Your app decides whether to show a button, open a browser link or download the file. AuthlyX does not install a release for the customer.

## Set up a test release

1. Open the app's **Updates** settings and keep **Stable** as the default.
2. Add a **Beta** channel with version `2.5.0-rc.1`, its download URL and release notes.
3. Open the test users, licenses or devices and assign them to Beta. Leave customers on Stable.
4. Sign in once with a test identity and once with a Stable identity. Check that the two sign-ins receive different release details.
5. When the test is approved, publish the version to Stable. Move test identities back to Stable if they should follow the public release.

## What a channel controls

A channel answers: **which release details should this identity receive?** The assignment is read after sign-in, when AuthlyX knows the identity. Linked user and license records share an assignment. A plan can set the default for new identities; changing that default does not move existing identities.

**Allowed Versions** answers a different question: **may the version already running connect?** A Beta identity can receive a link to `2.5.0-rc.1` while Allowed Versions still accepts `2.4.0`. If you need to stop `2.3.0` from signing in, change Allowed Versions too.

## When a channel is useful

Use channels when you want a small group to test a release without changing the update shown to everyone. If every customer should receive the same release, keep one Stable channel. A channel does not select a plan, change expiry or silently downgrade a customer's app.