Google Sign-In

The Google Auth tab lets people sign in with their own Google account instead of typing a password — useful if your team already lives in Google Workspace. It's additive: the regular username/password login keeps working exactly as before, on every plan.

Plan requirement

Google Sign-In is available on Plus and Pro. On Free, the tab is visible but every field is disabled, with a note explaining the plan requirement — see License for how to check or change your plan.

Bring your own OAuth Client

Chomper doesn't run a shared Google identity broker — each install connects to its own Google Cloud OAuth Client, under your own domain. That keeps sign-in working even if Chomper's own servers are unreachable, and means Google never sees Chomper as a middleman.

Setting it up

1. In Google Cloud Console, create or open a project.
2. Configure the OAuth consent screen (Internal is enough if everyone signing in is on your own Workspace domain).
3. Under Credentials, create an OAuth Client ID of type Web application.
4. Add the Authorized redirect URI — the tab shows this pre-filled for your exact install, with a Copy button, so there's nothing to type by hand.
5. Paste the resulting Client ID and Client Secret back into the tab, toggle Enabled, and save.

Use Test credentials to confirm a Client ID/Secret pair is valid before saving — it checks directly with Google, no real sign-in needed. For the full walkthrough on Google's side, see their own Setting up OAuth 2.0 guide.

Restricting to your own domain

The optional Hosted domain field limits sign-in to accounts on one Google Workspace domain. Leaving it empty accepts any Google account, including personal @gmail.com ones — worth setting if your team is on Workspace.

Who can actually sign in

Google Sign-In never creates a new account on its own. The email Google reports has to match an existing user's username exactly (case-insensitive) — anyone without a matching account gets a clear “no account found” message instead of being let in. See Users & roles for adding people and, if a username isn't already in email form, renaming it in place with the inline edit on that page.

After the first successful sign-in, Chomper remembers the Google account itself, not just the email — so a later email change on the Google side won't silently move the login to a different local account.

Falling back to a password

Google Sign-In is additive, not a replacement. If it's misconfigured, disabled, or Google itself is unreachable, the regular password login on the same page keeps working exactly as before.