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

# Allowed Versions

> Choose which versions of your app may sign in.

You release **Northstar Editor 3.2.0** after fixing a bug that caused projects to fail to save. You want users to move off `3.1.0`. Add `3.2.0` to the app's **Allowed Versions** list and remove `3.1.0` when you are ready to block it. A client on `3.1.0` then gets a `UPDATE_REQUIRED` response instead of a session.

```mermaid
%%{init: {"theme":"base","themeVariables":{"primaryColor":"#ffffff","primaryTextColor":"#171717","primaryBorderColor":"#404040","lineColor":"#606060","secondaryColor":"#f5f5f5","tertiaryColor":"#ffffff","edgeLabelBackground":"#ffffff"}}}%%
flowchart LR
  A[App sends version 3.2.0] --> C{Version in Allowed Versions?}
  B[App sends version 3.1.0] --> C
  C -->|Yes| D[Continue normal sign-in checks]
  C -->|No| E[Return UPDATE_REQUIRED]
  E --> F[App shows update instructions]
```

## Set the allowed list

1. Open the app's **Settings → Allowed Versions** page.
2. Add each exact version string your app sends during initialization, such as `3.2.0`.
3. Keep the list empty if you want every version to pass this check. Once you add entries, only listed versions are accepted.
4. Test an allowed build and a build you intend to block before changing production access.

Before removing a version, publish a working update and tell affected customers where to get it. An app that receives `UPDATE_REQUIRED` should show an update message or link. It should not close without explanation.

## How this differs from other release settings

* **Allowed Versions** decides whether the version currently running may connect.
* **Release Channels** decides which update link and release notes a signed-in identity receives.
* **Hash Management** checks a build hash. A version string is not a fingerprint of the executable.

For example, you can offer Beta `3.3.0-rc.1` to testers while both `3.2.0` and `3.3.0-rc.1` remain allowed. When you later remove `3.2.0`, it is rejected even if the customer is still assigned to Stable.