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

# Choose how customers sign in

> Pick license, username and password, or device login for your app.

A sign-in method is what your customer uses to prove they have access to MyApp. You can offer license login, username and password, device login, or a combination. There is no single best choice for every product.

```mermaid
flowchart TD
    A[You choose which methods MyApp offers] --> L[License login]
    A --> U[Username and password]
    A --> D[Device login]
    L --> L1[Customer enters their license, such as ADE]
    U --> U1[Customer enters their username and password]
    D --> D1[MyApp reads the configured processor or motherboard identifier]
    D1 --> D2[The matching identifier must be whitelisted in Devices]
    L1 --> C[AuthlyX checks the matching access record and app rules]
    U1 --> C
    D2 --> C
    C --> OK[Allowed: issue an authenticated session]
    C --> NO[Rejected: return the reason]
```

## License login

You create a license and give its value to the customer. MyApp submits that value when they sign in. A license can be generated in groups such as `ADE2-44R4-YY3W-554D`, but it can also be your own string, such as `ADE`. The grouped format is a convenience, not what makes a value a license.

You can build a Remember me option for a license, just as you can for a username. Store credentials carefully and explain what is saved. Remembering a key does not make an expired or banned license valid.

## Username and password

The customer signs in with a username and password. Some developers prefer this because it gives customers familiar login details and password-management options. A developer can create the user, or use the supported registration flow with a license. The exact registration behaviour is explained in the SDK and API references.

This method is not automatically better for multiple devices. Device limits and the records you configure determine access, whichever sign-in method you offer.

## Device login

MyApp sends an identifier that you have whitelisted. The customer does not type a license, username or password. For your hardware-based workflow, use the chosen motherboard or processor identifier consistently in the whitelist and the app.

**Current V3 integration detail:** the API receives the configured identifier in `sid`. The SDK's Windows default helper reads a Windows account SID; it does not automatically read a motherboard or processor ID. Configure the intended identifier instead of treating the default SID as a hardware serial. See [Device login](/v3/guides/device-login).

## Offer one, two or all three

Your interface can show only License login, only Username and password, or several choices. For example, MyApp might offer keys to individual customers and device login on preapproved workstations. The same application can support both.

Choose the experience you want to sell and support. AuthlyX checks the record behind the selected method, its expiry and status, device limits and application policies. Your app must use the returned result before opening protected features.