Multi-Factor Authentication (MFA)
Multi-factor authentication (MFA) is one of the most effective ways to protect your SingleSign account. It adds a second verification step so that even if someone learns your password, they still can't sign in.
What is MFA?
MFA requires two factors to sign in:
- Something you know — your password.
- Something you have — a time-based one-time password (TOTP) generated by an authenticator app on your phone.
After you enter your password, you'll be asked to enter a 6-digit code from your authenticator app. This code changes every 30 seconds, so it can't be reused.
How to enable MFA
- Sign in to your SingleSign account at singlesign.com.
- Go to Account → Security → MFA.
- Click "Enable".
- Scan the QR code with your authenticator app.
- Enter the 6-digit code displayed in your app to confirm setup.
- Save your backup codes — you'll be shown a set of one-time backup codes. Store them in a safe place (like a password manager or a printed copy in a secure location). You'll need these if you ever lose your authenticator device.
Using MFA to sign in
- Enter your email and password as usual.
- When prompted, open your authenticator app.
- Enter the 6-digit code currently displayed in the app.
- You're signed in.
Supported authenticator apps
SingleSign works with any TOTP-compatible authenticator app, including:
- Google Authenticator (Android, iOS)
- Authy (Android, iOS, Desktop)
- 1Password (all platforms)
- Microsoft Authenticator (Android, iOS)
- Bitwarden (all platforms)
Lost your MFA device?
If you've lost the device with your authenticator app:
- On the sign-in page, click "Use a backup code" instead of entering an MFA code.
- Enter one of your backup codes. Each code can only be used once.
- Once signed in, go to Account → Security → MFA and set up MFA again with your new device.
- Generate a new set of backup codes after re-enabling MFA.
If you don't have any backup codes, see Recovery options for alternative ways to regain access to your account.
Last updated: 2026-02-16
Related articles
- Help CenterFind answers about using SingleSign to sign in, manage your privacy, and secure your account.
- Recovery Options, step by stepHow to set up recovery contacts and backup codes to ensure you can always access your SingleSign account.
- Identity provider security, by designIdentity provider security at SingleSign: PKCE-protected code exchange, redirect URI allow-lists, MFA, session and device control, and rate limiting.
- free identity providerSingleSign pricing in one line: sign-in is free, with no monthly-active-user meter. See exactly what is included, and what SingleSign Mail costs for businesses.
- Identity provider alternativesIdentity provider alternatives, by the provider you are leaving: what actually has to change in your code, and what does not.
- Auth0 comparisonSingleSign vs Auth0 compared on the difference that matters: who owns the account. A side-by-side table, then the three cases where each one is the right call.
- SingleSign vs OktaSingleSign vs Okta: Okta is built for workforce identity inside a company, SingleSign for consumer sign-in across applications.
- Firebase Auth comparisonSingleSign vs Firebase Authentication on lock-in, portability and consent, plus the cases where staying on Firebase is right.
- Google Sign-In alternativeSingleSign vs Google Sign-In: the same one-tap convenience, without an advertising business behind the identity.
- Auth0 alternativesAuth0 alternatives compared, plus the part most listicles skip: what migrating off Auth0 actually involves, which code changes, and which does not.
- alternative to OktaOkta alternatives for teams that need customer sign-in rather than workforce identity. The table first, then what changes when you move consumer auth off Okta.
- alternative to Firebase AuthFirebase Authentication alternatives for teams leaving Google Cloud or wanting a standalone OIDC provider. Comparison table, then the real migration path.