Skip to main content
This page documents Google authentication for your app’s users. It is available only for apps using the built-in backend. For an overview of all sign-in methods, see Users and authentication.
Sign in with Google lets people sign in with the Google account they already have, instead of creating a password for your app. Google has already verified their email address and passes it to your app.
Building an internal tool for your own workspace members? On Business and Enterprise, your app can recognize members who are logged in to Lovable, with no Google sign-in at all. See Reuse Lovable workspace identity in your app.

Choose a setup option

Users sign in the same way with both options. The options differ in who manages the credentials and what Google’s consent screen shows.
With Managed by Lovable, Google’s consent screen shows Lovable as the app that requests access. The first time a user signs in to your app, Lovable also shows its own consent page with your project’s name, which asks the user to share their email address and basic profile information.After the user approves, they return to your app, signed in. Lovable’s consent page does not appear again after their first sign-in to your app.
1

Ask Lovable to add Google sign-in

In the project chat, ask:
Lovable enables Google sign-in in More → Users → Settings → Google. Lovable also adds the sign-in flow to your app: the Sign in with Google button, tracking who is signed in, and signing out. You can review the changes in the Details view.
2

Test the flow

Verify that:
  • a Sign in with Google button appears on your login page
  • users are redirected to Google to sign in
  • users return to the app in a signed-in state
  • users can sign out

Managing Google authentication

You can switch between Managed by Lovable and Your own credentials at any time from More → Users → Settings → Google. Switching does not affect existing user accounts, so users keep signing in with the same Google accounts. To stop offering Google sign-in, disable the provider in the auth settings. Lovable then sends a message to the project chat on your behalf and removes the Google sign-in button from your app. That message is treated as standard build usage and consumes credits. Users who signed up with Google keep their accounts but need another enabled sign-in method to get back in. If you use your own credentials and connect a custom domain later, Lovable adds a redirect URL for that domain to the list in More → Users → Settings → Google but does not select it, so Google sign-in keeps using your other selected redirect URIs. To use the new one, add it as an Authorized redirect URI on your OAuth client in Google Cloud Console first, then select it in Lovable and click Save. If you select it before you add it in Google Cloud, Google sign-in fails with a redirect URI mismatch error. Managed by Lovable needs no change when you connect a domain.
Some projects that set up their own credentials earlier show a third option, (Legacy) Your own credentials. (Legacy) Your own credentials is deprecated. Switch to Your own credentials to get automatic updates and the current branding and security features.

Troubleshooting your own credentials setup

The redirect URIs you selected in Lovable do not match the Authorized redirect URIs on your OAuth client. Add every URI you selected in Lovable to Google Cloud, and check that each one matches exactly, including the scheme (https) and any trailing slash.
Lovable’s redirect flow needs an OAuth client of type Web application. Mobile and desktop client types do not work with it. Create a Web application client and enter its credentials in Lovable.
Check that Google sign-in is enabled in More → Users → Settings → Google, and that the Client ID and Client secret match your OAuth client. If both are correct, ask Lovable in the project chat to check that your app’s sign-in button is connected to the backend.

FAQ

No. Managed by Lovable Google authentication is available only for apps using the built-in backend.
Yes, but you set it up yourself outside Lovable. For example, you might:
  • integrate Google OAuth directly in your frontend or backend code
  • use Google’s One Tap or standard OAuth sign-in flows
  • use a third-party authentication service such as Supabase Auth
  • manage OAuth credentials, redirect handling, and sessions yourself
This page covers Google sign-in on the built-in backend only.
Use Managed by Lovable unless you specifically need to manage your own Google Cloud OAuth credentials or customize the consent screen branding.
Google provides the user’s email address and basic profile information. Your app does not get access to other data in the user’s Google account, with either setup option.
Yes. You can switch between Managed by Lovable and Your own credentials at any time. Existing user accounts are not affected.
The redirect URLs you selected in Lovable usually do not exactly match the Authorized redirect URIs in Google Cloud.
  • Add every redirect URL you selected in Lovable to Google Cloud.
  • Check the scheme, domain, path, and trailing slashes.
No. Google authentication is an additional sign-in method. You can offer Google sign-in alongside other authentication methods.
Not when Google’s native sign-in uses a separate client ID for the app. Lovable accepts one client ID for Google sign-in: its own with Managed by Lovable, or the one you enter with your own credentials. Instead, have the app open Google sign-in in the browser. Add the app’s custom scheme, such as myapp://callback, to Redirect URLs in the auth settings. See Site URL and redirect URLs.
No. You configure Google Cloud Console only when you use your own credentials.