Set up Sign in with Google — Knowledge base

Google sign-in works in AuthRobo two ways. This guide answers the most-asked question first, then walks you through creating your own Google app against the current Google Cloud Console, screen by screen.

"Why does it say AuthRobo instead of my app?"

When you enable Google without entering your own credentials, AuthRobo uses its shared Google app so you can ship in seconds. The trade-off: Google's consent screen reads "AuthRobo wants access to your account", because — as far as Google is concerned — the app asking is AuthRobo's.

To make that screen show your name and logo, you create your own Google OAuth client (a client_id and client_secret) and paste it into AuthRobo. Nothing about your app's code changes — it's a dashboard change only. (More on the two modes: Shared vs bring-your-own.)

This is different from your AuthRobo client secret. These are Google's credentials, identifying a Google app to Google. If that distinction is fuzzy, read Your credentials & env vars first.

Before you start

A Google account with access to the Google Cloud Console.
Your app's AuthRobo callback URL — copy it from the Google setup panel in your AuthRobo dashboard. It follows our convention https://<your-domain>/api/v1/auth/google/callback. Throughout this guide we use `example.com` as the stand-in for your domain.

Step 1 — Create a new project

In the Google Cloud Console, open the project picker at the top and click New project. Give it a name (e.g. your product name) and create it. Everything below happens inside this project.

Google Cloud Console — create a new project

Step 2 — Create an OAuth client (Web application)

Go to Clients → Create client (under APIs & Services). For Application type, choose Web application.

Create OAuth client ID — Application type set to Web application

Step 3 — Set the URLs (use your domain + our API convention)

Fill in the two URL fields using your domain. With example.com as the stand-in:

Authorized JavaScript origins: https://example.com
Authorized redirect URIs: https://example.com/api/v1/auth/google/callback

Copy the exact callback from your AuthRobo dashboard so there's no typo, trailing slash, or http/https mismatch.

Authorized JavaScript origins and redirect URIs set to example.com

The redirect URI must be AuthRobo's callback (/api/v1/auth/google/callback), not your app's own login page. Google returns users to AuthRobo, which then returns them to your app. See Redirect URIs: the two callbacks.

Step 4 — Download the client details JSON

After you create the client, Google offers a Download JSON of the client details. Download it and keep it somewhere safe — it contains your Client ID and Client secret. (You'll paste those two values into AuthRobo in the last step.)

Step 5 — Open Data access (scopes)

In the left nav, open Data access, then click Add or remove scopes. Scopes are the permissions your consent screen asks users to approve.

Data access page with Add or remove scopes

Step 6 — Choose the three non-sensitive scopes

AuthRobo only needs identity basics. Tick exactly these three non-sensitive scopes, then Update:

openid — associates the user with their Google account
.../auth/userinfo.email — the user's email address
.../auth/userinfo.profile — the user's name and avatar

That's the whole of openid email profile. Leave the sensitive and restricted scopes untouched — requesting them triggers extra Google review you don't need.

Update selected scopes — openid, userinfo.email and userinfo.profile ticked

Step 7 — Branding & verification (to publish)

While your app is unpublished / in testing, only the test users you list can sign in. To let any Google user sign in, you publish the app — and Google won't verify it until the Branding section is complete. You'll need:

An app name and logo that match your brand (and match across the consent screen — Google checks for consistency).
A valid, final Privacy Policy URL and Terms of Service URL (live pages on your domain, not placeholders).
Verified ownership of your domain via Google Search Console — add and verify example.com there, then it can be used here.

Branding, privacy/terms links and verified domain for publishing

Verification can take a few days once submitted. Until then you can keep testing with listed test users — sign-in still works for them.

Step 8 — Paste the credentials into AuthRobo

Back in AuthRobo: open your app → Google setup panel → paste the Client ID and Client secret (from the JSON in Step 4), tick Enable Google sign-in, and Save.

AuthRobo Google setup panel with the Client ID and secret pasted and enabled

Done. The next Google sign-in shows your brand on the consent screen instead of "AuthRobo".

Troubleshooting

"redirect_uri_mismatch" → the redirect URI in Step 3 doesn't match AuthRobo's callback character-for-character. Re-copy it from the dashboard.
Still says "AuthRobo" → you're still on the shared app; make sure Step 8 saved your credentials and Google is enabled.
"Access blocked / app not verified" → your app is unpublished or the signer isn't a listed test user. Add the tester, or complete Step 7 and publish.
Can't verify the domain → do it in Google Search Console first (DNS TXT or HTML file), then return to the Branding section.

Ready to build? Create your app → or browse the API reference.