Sign-in methods overview
- Written for
- ＋ Written for
- Deprecated
- ＋ Deprecated
- Applies to
- ＋ Applies to
Sign-in methods overview
Atlas supports the full range of modern sign-in methods. You choose which ones to offer, and Atlas renders them all in one coherent flow — whether you use the hosted pages, the embed widget or the SDK.
The methods
Method | Best for | Page |
|---|---|---|
Password | Familiar, works everywhere | |
Email / SMS codes | Passwordless, low friction | |
Magic links | One-click email sign-in | |
Social / OAuth | Reuse existing accounts (56 providers) | |
Passkeys (WebAuthn) | Phishing-resistant, no password | |
Sign in with Ethereum | Web3 / wallet-based apps | |
Multi-factor (MFA) | A required second factor |
How the flow advances
Atlas runs sign-in as an attempt that advances one step at a time. It picks the strategies your instance allows and only asks for what's needed:
Identifier — the user enters an email, phone or username (or picks a social provider / passkey straight away).
Strategy — Atlas offers the factors you've enabled for that identifier.
Verify — the user completes one factor.
Step-up MFA — if required, a second factor.
Session — Atlas issues a signed session and returns the user to your app.
Because the server drives the flow, the same rules apply on every path — including social sign-in — so you can't accidentally skip MFA or a required factor.
Turning methods on and off
Open Sign-in methods for the selected instance.
Toggle each method on or off.
For social and enterprise connections, open Connections to add credentials.
Save. Changes apply to the hosted pages, the widget and the SDK immediately.
Enable at least one method that lets a brand-new user create an account (for example, email code or a social provider). You can mix and match freely — many products offer social + email code + passkey together.
Next
Start with the classic → Passwords.