Multi-Factor Auth That Users Don’t Hate

Turning MFA on is a one-line change. Getting people to use it is a product problem, and most rollouts fail at exactly the same place: the team makes it optional, buries it in settings, and then reports six percent adoption as though the feature were at fault.

Ask at the right moment

Nobody enables MFA while trying to do something else. The prompt lands when the user has just done something that made them feel the value of the account — invited a colleague, connected a payment method, uploaded real data. That is when protecting it feels obvious rather than bureaucratic.

Then get out of the way

• Remember trusted devices. Prompting on every login trains people to turn it off.
• Step up instead of blanket-prompting: require the second factor for sensitive actions, not for reading a dashboard.
• Issue recovery codes at enrolment and make people acknowledge them.
• Have a support path for lost devices before you launch, not after the first ticket.

MFA is available from the Starter plan in Alt Auth and is configured per project, so you can require it for staff-facing applications and leave it optional for consumer ones.

See plans with MFA →