This page documents email authentication settings for apps using the built-in backend. Projects connected to your own Supabase project manage authentication in Supabase instead. For an overview of all sign-in methods and user management, see Users and authentication.
How email sign-in works for users
- Signing up: the user enters an email address and password. Unless auto-confirm is enabled, they receive a confirmation email and verify the address before they can sign in.
- Signing in: email and password, or a passwordless flow if you build one.
- Resetting a password: the user requests a reset, receives a password reset email, and picks a new password.
- Changing an email address: with secure email change enabled, both the old and new address must confirm the change.
Passwordless sign-in
Email sign-in can also work without passwords. Ask Lovable in the project chat to build a magic link or one-time code flow instead:Email confirmation
Two settings control how addresses are verified:- Auto-confirm email: sign users in immediately without requiring them to confirm their email address. With auto-confirm disabled, users receive a confirmation email and must verify the address before signing in.
- Secure email change: require confirmation on both the old and new address when a user changes their email.
Password rules
Five settings control how strong passwords must be:- Minimum password length: at least 6 characters. A minimum of 8 is recommended.
- Required password characters: which character types every password must include. The default, No required characters, adds no requirement beyond the minimum length. The stricter options are Letters and numbers, Lowercase, uppercase, and numbers, and Lowercase, uppercase, numbers, and special characters.
- Password HIBP check: reject known or easy-to-guess passwords using the Have I Been Pwned database of leaked passwords. Enabled by default on new projects.
- Require re-authentication for password changes: require a recent login before a password can be changed.
- Require current password for password changes: users enter their current password to set a new one. Enabled by default on new projects.
One-time codes
For login flows that email a one-time code instead of using a password:- Email OTP expiration (seconds): how long a code or magic link stays valid, from 60 seconds to 24 hours.
- Email OTP length: 6 to 8 digits.
Sending limits
Rate limit for sending emails, found in More → Users → Settings → Email → Advanced, caps how many authentication emails your project sends per hour. New projects start at 1,000 emails per hour when the project’s email sending is active. If your app signs up many users at once and confirmations stop arriving, this limit is the first thing to check. To raise the limit above 1,000, for example before a launch, enter a higher value yourself, up to 32,767 emails per hour. When you ask in the project chat, Lovable can set the limit up to 1,000 emails per hour. If Lovable says your project’s email sending is not active, set up custom emails first. Until then, authentication emails go through a shared sender with its own strict limit, so a higher value does not get more emails delivered. Rate limit for sending emails is the only authentication rate limit you can change in Lovable. When your project sends authentication emails from your own domain, they also count toward your workspace’s hourly limit for authentication emails, which depends on your plan. See Custom emails.Troubleshooting
Users are not receiving confirmation emails
Users are not receiving confirmation emails
Ask users to check their spam folder first, since emails from new domains often land there. If many signups happen at once, your project may have exceeded its hourly email rate limit. For better deliverability and branded senders, set up custom emails.
Sign-in works in preview but fails on the published app
Sign-in works in preview but fails on the published app
The published URL or custom domain is probably missing from your project’s redirect URLs. See Site URL and redirect URLs.
A user is stuck unconfirmed
A user is stuck unconfirmed
Their confirmation email may have expired or landed in spam. Signing in again does not resend it. To get a new confirmation email, the user signs up again with the same email address.You can also create the account for them: users added with Add user → Create new user in More → Users are confirmed automatically.
FAQ
Should I turn on auto-confirm email?
Should I turn on auto-confirm email?
Auto-confirm is convenient while building and testing, because you can create accounts without checking an inbox. For a live app, keep confirmation enabled so every account belongs to a real, verified address.
Can users sign in without a password?
Can users sign in without a password?
Yes. Ask Lovable to build a magic link or one-time code flow: users receive an email and sign in without typing a password. The One-time codes settings control how long codes stay valid and how many digits they have.
Can I turn off email sign-in entirely?
Can I turn off email sign-in entirely?
How do password resets work?
How do password resets work?
Lovable generates the reset flow when it builds email sign-in: users request a reset, receive a password reset email, and choose a new password. You can customize the reset email under More → Emails.
Where do I customize the emails users receive?
Where do I customize the emails users receive?
Signup confirmations, password resets, invites, and magic links are sent using your project’s email templates. Set up sending from your own domain and preview each template under More → Emails. See Custom emails.