Members: sign in with your site's own Google client
Create an OAuth client in your own Google Cloud project so Google's sign-in screen shows your site instead of SeedWebs.
By default members sign in with Google through SeedWebs' client, so Google's account picker says SeedWebs. To show your site's name instead, create an OAuth client in your own Google Cloud project and add it to your site's settings.
Before you start
-
Your site needs a custom domain that is connected and active (on a plan that includes one): Google must send people back to your
own domain. A site still on
yoursite.seedwebs.appkeeps signing members in with SeedWebs' client. - In the admin, open Members ▸ Login settings, tab Sign-in methods, with Google turned on. Under the Google row are the values to enter in Google Cloud, with copy buttons (admins only).
- A Google account to create the Google Cloud project with.
1. Create a Google Cloud project
- Open the Google Cloud Console, click the project picker at the top ▸ New project.
- Name it (your site's name, for example) and click Create.
2. Set up the OAuth consent screen
Under APIs & Services ▸ OAuth consent screen (Google calls this area the Google Auth Platform):
- Branding: enter the App name (your site's name), a support email, a logo (optional), your home page
https://your-domainand your privacy policy link. Under Authorized domains add the Authorized domain shown on the admin card. - Audience: choose the External user type and click Publish app so the status is In production. (While it is in Testing, only accounts added as Test users can sign in.)
- Data access: keep to the basic scopes
openid,emailandprofile, and add nothing else. Those need no app verification and have no user cap.
Google shows your app name and logo on its consent screen only after brand verification, which asks you to prove you own the domain in Google Search Console with an account that is an owner or editor of the project. Members can sign in as usual while you wait.
3. Create the OAuth client
- Go to Clients (or Credentials) ▸ Create client and choose the Web application type.
- Authorized JavaScript origins: add
https://your-domain(copy it from the card's Authorized JavaScript origin). - Authorized redirect URIs: add
https://your-domain/api/member/auth/callback(copy it from the card's Authorized redirect URI). It must match exactly. - Click Create and copy the Client ID and Client secret.
4. Test and save in SeedWebs
- Back in Members ▸ Login settings ▸ Sign-in methods ▸ Google, paste the Client ID and Client secret.
- Press Test and save. Google opens in a new tab: sign in there with any Google account.
- When that tab says Google connection works, the client is saved and you can close it. Back on the settings page the status reads Using your site's own Google client. The test creates no member and signs nobody in.
- Once saved, the Client ID shows as text and the Client secret stays hidden; neither can be edited in place. To use another client, press Change client. The current client stays in use until the new one passes its test.
- If the test fails, nothing is saved and members keep signing in through SeedWebs' client.
| What Google says | Usual cause |
|---|---|
redirect_uri_mismatch | The Authorized redirect URI in Google Cloud is not exactly the one on the card (a missing https, a trailing /). |
invalid_client | The Client ID or Client secret is wrong or was copied only in part. |
access_denied | Cancel was pressed on Google's page, or the app is still in Testing and that account is not a Test user. |
When the domain changes or goes away
Members can always sign in: when your client cannot be used (the domain changed or was disconnected, or the plan no longer includes a custom domain), sign-in switches to SeedWebs' client by itself, and you are told three ways — a banner on the dashboard, the status on the Google card and one email to the site owner.
To use your client again, add the new domain's Authorized JavaScript origin, Authorized redirect URI and Authorized domain in Google Cloud (the card shows them), then press Test again. It uses the saved Client secret.
Existing members
Members are matched by email, and Google gives an account the same ID whichever client it signs in with, so switching between SeedWebs' client and yours changes nothing for existing members.
Stop using your client
Press Go back to SeedWebs' client under the Google row and confirm. Your saved client is deleted, and members sign in with SeedWebs' client again at once.