Google sign-in
Continue with Google works out of the box. Use your own Google OAuth client to put your brand on the consent screen.
Last updated September 17, 2026
On this page
Continue with Google is on for every new app. A visitor who signs in with Google for the first time gets an account in your app; an existing email-and-password account that uses the same address is linked, not duplicated.
Two ways to run it
| Option | What the user sees | Setup |
|---|---|---|
| Praxivara's Google sign-in | Google's consent screen with Praxivara's name | None. On by default. |
| Your own Google OAuth client | Your app's name and logo on the consent screen | Create a client in Google Cloud and paste its ID and secret. |
Using your own client
In the Google Cloud console, create an OAuth client of type Web application.
Under Authorized redirect URIs add exactly the address shown under Settings › Authentication › Google in your dashboard. No authorized JavaScript origin is needed; sign-in happens by redirect.
Set the consent screen's app name and logo to your brand. That is what your users see.
Under Settings › Authentication choose Use your own Google OAuth client, paste the Client ID and Client secret, and press Update. Praxivara checks them with Google before saving.
The secret is stored encrypted and never shown again; the dashboard keeps only its last characters as a hint.
In the builder preview
Google will not open inside the preview frame, so the button shows a short note there. You are already signed in as the owner in the preview, so nothing is lost. On the published app the button works normally.
Turning it off
Switch Google off under Settings › Authentication. People who registered with Google can set a password through the forgot-password page if email sign-in is on.