Prompt
How do I support MFA without making sign-in too annoying for customers?
Latest observation
Oct 28, 2026
OpenAI APIWeb search: off
To support MFA without making sign-in feel painful, aim for risk-based, low-friction MFA rather than forcing a challenge every time.
Practical approach
1. Use MFA only when it adds value
Trigger MFA for:
- New device or browser
- Unusual location/IP
- Sensitive actions like changing password, adding a payout method, exporting data
- Admin or privileged accounts
- Re-authentication after long inactivity
Avoid prompting on every login if the session is already trusted.
2. Offer multiple MFA methods
Give users choices:
- Authenticator app or passkeys as primary options
- SMS only as a fallback, not the default
- Backup codes for recovery
Passkeys are especially good because they’re both secure and low-friction.
3. Remember trusted devices carefully
Let users “trust this device” for a limited time, such as 30 days, but:
- Bind trust to device/browser fingerprint plus a secure token
- Re-check on major changes
- Allow users to revoke trusted devices from account settings
4. Make step-up authentication contextual
Instead of asking for MFA at login, ask only when:
- Risk score is high
- Action is sensitive
- The account is doing something unusual
This preserves security while reducing routine interruptions.
5. Design a good recovery flow
MFA becomes annoying when users get locked out. Help with:
- Backup codes
- Recovery via verified email/phone
- Support-assisted recovery with strong identity checks
- Clear guidance during setup
6. Keep enrollment easy
During onboarding:
- Explain why MFA matters in plain language
- Make setup fast, with a QR code for app enrollment
- Let users skip temporarily if appropriate, but keep nudging them later
7. Tune prompts based on customer type
- Consumers: prioritize passkeys and “remember this device”
- B2B / enterprise: require MFA for admins and high-risk roles
- High-risk transactions: always step up
8. Measure and iterate
Track:
- MFA enrollment rate
- Challenge success rate
- Drop-off during login
- Recovery requests
- Fraud prevented vs. friction added
Use those metrics to adjust when prompts appear.
A good default policy
A balanced setup often looks like:
- Primary sign-in: password + passkey or password + app-based MFA
- Trusted device: no MFA for routine logins for a limited period
- Risky event: step-up MFA
- Recovery: backup codes + secure support flow
If you want, I can also give you:
- a recommended MFA policy for SaaS products, or
- a sample login flow that minimizes customer friction.