Teams should treat passkey sign-in as device-initiated, not username-initiated. Present available passkeys as soon as the user focuses the sign-in field or opens the authenticator flow, then use the credential’s internal identifier to find the account. If no passkey is available, fall back to a familiar passwordless path such as email OTP or magic link.
Why passkey sign-in should start from the device, not a typed username
Passkey UX works best when the browser or app can surface credentials before the user has typed anything. That removes a common friction point, avoids asking users to remember which account they used, and lets the authenticator choose the right credential through its own local identifier and user verification. The sign-in flow should therefore be designed around credential discovery, not account lookup.
That approach also fits how passkeys are meant to behave across platforms. When the user opens the sign-in flow, the system can show available passkeys immediately, then let the user pick the right one or verify with biometrics, PIN, or another local unlock method. The account is resolved after the credential is presented, not before.
For implementation, the practical test is simple: if a user must type a username to reach the passkey prompt, the flow is still too password-shaped. Teams should make the first interaction a passkey chooser, a field that triggers passkey discovery, or a device prompt that can discover stored credentials without the user first supplying account identity.
How to handle account discovery and fallback paths
Once a passkey is selected, the relying party can use the credential’s internal identifier to map the response to the correct account. That means the application needs a lookup path that accepts the passkey result as the primary signal and only falls back to username entry when no usable passkey is available or the user is intentionally choosing another sign-in method.
The fallback should be familiar and low-friction, but it should not distort the passkey path. Email OTP or a magic link can be a reasonable backup for users who have no registered passkey on the device, provided the product keeps the passkey route prominent. If the fallback becomes the default because discovery is awkward, users will quickly learn to bypass the passkey experience.
Teams also need to think about multi-account and shared-device cases. A good discovery flow should help users distinguish between work and personal accounts, show which passkeys are available on the current device, and avoid confusing them with duplicate prompts. That is especially important when the same browser profile or password manager can surface more than one eligible credential.
What good passkey UX must get right in practice
Passkey sign-in should reduce both cognitive load and support burden, but only if the experience is consistent across entry points. The same discovery logic should work when the user taps the sign-in field, returns from a QR or cross-device flow, or opens an authenticator chooser from a mobile device. Inconsistent handling is where users start to feel that passkeys are unreliable.
Use the passkey’s identifier and the platform’s built-in account selection behaviour to avoid creating a second identity-picking step inside your own application. Where possible, let the authenticator and browser do the credential discovery work, and keep your own UI focused on recognition, recovery, and clear fallback choices. For implementation details around credential handling and WebAuthn behaviour, FIDO2 and WebAuthn Internals Guide is the most direct technical reference.
Teams rolling out passwordless flows should also align the UX with their broader authentication strategy. If you need a fuller view of phishing-resistant sign-in, recovery and rollout decisions, Passwordless and Passkeys Guide explains the surrounding design choices, while NIST SP 800-63 Digital Identity Guidelines provides the current identity assurance context for phishing-resistant authentication.
Risk and Threat Considerations
When passkey flows are forced to begin with username entry, teams reintroduce avoidable friction and make the experience more vulnerable to account enumeration, poor fallback habits, and user confusion. The result is often not a broken cryptographic control, but a broken journey that pushes users toward weaker recovery paths or inconsistent account selection.
Failure mechanism: The product treats passkeys like a password replacement instead of a discoverable credential, so the user must supply an identifier before the authenticator can help. That can expose account-lookup behaviour, create unnecessary dead ends for users with multiple accounts, and encourage fallback use even when a passkey is available.
Impact: Users abandon the stronger flow, support tickets rise, and the organisation loses the practical security benefit of passkeys because the login experience still behaves like legacy username-first authentication.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-63, OWASP ASVS, NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-63 | Digital Identity Guidelines | Passkey-first discovery and phishing-resistant sign-in are central identity guidance topics. |
| Recommendation — Align the sign-in flow to phishing-resistant authentication and account discovery guidance. | ||
| OWASP ASVS | V10 — OAuth and OIDC | Passkey-backed login flows often integrate with modern auth flows and account selection behavior. |
| Recommendation — Verify the authentication flow supports safe credential discovery and account selection. | ||
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Passkey onboarding and fallback handling depend on secure authenticator lifecycle management. |
| IA-2 — Identification and Authentication (Organizational Users) | The question is about how users authenticate into an application without username-first entry. | |
| Recommendation — Manage authenticators so users can enroll, use, and recover passkeys safely. Design sign-in so identity is confirmed through the authenticator, not manual account entry. | ||
| CIS Controls v8 | 5 — Account Management | Passkey sign-in changes how accounts are discovered, selected, and recovered. |
| Recommendation — Centralise account discovery and recovery so passkey users can authenticate cleanly. | ||
Practitioner Guidance
What to verify: Test the first-click experience end to end. A user who already has a passkey should be able to reach credential discovery without typing a username, and the account chosen by the system should be unambiguous when multiple passkeys exist.
Decision rule: If the user cannot start sign-in from the credential itself, redesign the flow before launch. Keep fallback paths available, but do not let them become the primary route when passkey discovery fails for interface reasons rather than genuine credential absence.
Practitioner takeaway: Good passkey design removes the username as a prerequisite for discovery, because the user experience should begin with credential presentation and end with account resolution, not the other way around.
Related resources from NHI Mgmt Group
- How should teams design self-service onboarding so users can sign up and reach the application without manual hand-offs?
- How should teams design sign-up flows to reduce bot registrations without adding unnecessary friction for real users?
- What happens when existing users are migrated to passwordless sign-in without first verifying their current identity?
- How should SaaS teams authenticate users, partners, and workloads without mixing trust boundaries?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org