Two-Factor Authentication (2FA)

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want Two-Factor Authentication (2FA) working in a real project rather than a sandbox.

   Set up Two-Factor Authentication (2FA) in this project — authenticator app or SMS 2FA on every Lovable account. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Account hardening

   The record lists this as one of the jobs Two-Factor Authentication (2FA) is meant for, so it is a fair first test of whether it fits your app.

   In this project, use Two-Factor Authentication (2FA) for account hardening. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   Two-Factor Authentication (2FA) is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses Two-Factor Authentication (2FA) before I publish. Check TOTP authenticator app and SMS codes, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Shared workspace protection

   A second job the record lists for Two-Factor Authentication (2FA), useful once the first path works.

   Extend this project so Two-Factor Authentication (2FA) also covers shared workspace protection. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is Two-Factor Authentication (2FA)?

  Two-Factor Authentication (2FA) is Lovable's Security feature: Authenticator app or SMS 2FA on every Lovable account. Two-factor authentication via TOTP authenticator app (Google Authenticator, Microsoft Authenticator, Authy, 1Password) or SMS.

• Is Two-Factor Authentication (2FA) GA or in beta?

  Two-Factor Authentication (2FA) is generally available (GA) on Lovable.

• What Lovable plan includes Two-Factor Authentication (2FA)?

  Two-Factor Authentication (2FA) is available on all Lovable plans.

• When did Two-Factor Authentication (2FA) launch?

  Two-Factor Authentication (2FA) launched on Jan 16, 2026.

• Dependency Vulnerability ScanningSame category, also GA · Jan 2026
• Security CenterSame category, also GA · Jan 2026
• SCIM ProvisioningSame category, also GA · Feb 2026