Create a Google Cloud project and a Web application OAuth client, add Bevy’s authorized origins and redirect URIs, then send the Client ID and Client secret to Bevy over a secure channel so members can sign in with Google.
Bevy can show a Sign in with Google button on your community login and signup pages. Members authenticate with Google; Bevy then creates or signs in their community account.
Note: This page is for technical admins who create the Google OAuth client. For which social providers you can enable, see Introduction to social sign-on. Enterprise workplace SSO (Okta, Auth0, SAML, and similar) is separate — see Introduction to single sign-on. Members who use enterprise SSO follow Sign-in with single sign-on (SSO).
Tip: This setup is for Google login only. It is not Google Analytics, Google Tag Manager, or a marketing pixel. Sibling providers: Set up LinkedIn social sign-on, Set up Facebook social sign-on, Set up X social sign-on.
Before you start
- Access to the Google Cloud Console for the Google Cloud project that will own the OAuth client.
- Your Bevy community hostname (and staging or onboarding hostnames if Bevy asks you to whitelist them).
- A secure way to share the Client ID and Client secret with Bevy (for example a password manager share or encrypted message — not email in plain text).
Create the Google Cloud project and OAuth client
- Open the Google Cloud Console and select or create a project for this community.
- Configure the OAuth consent screen (Google Auth Platform) if Google prompts you. Use an app name members will recognize, and complete any required publisher and contact fields before you create a client.
- Open Clients (under Google Auth Platform) or APIs & Services → Credentials, then create a new OAuth client.
- Choose application type Web application and give the client a clear name (for example your Bevy community name).
Tip: Google’s console labels move over time. If you do not see Clients, look under APIs & Services → Credentials → Create credentials → OAuth client ID. The application type must still be Web application.
Add authorized origins and redirect URIs
On the Web application client, set both of the following for each Bevy hostname you use.
Authorized JavaScript origins
Add the community base URL only — scheme and host, no path:
| Environment | Authorized JavaScript origin |
|---|---|
| Bevy test / staging sandbox | https://<instance-id>-staging.bevylabs.com |
| Onboarding instance | https://<instance-id>.bevylabs.com |
| Production community domain | https://<your-community-domain> |
Example production origin: https://www.startupgrind.com
Authorized redirect URIs
Add Bevy’s Google callback path. Match the path exactly, including the trailing slash:
| Environment | Authorized redirect URI |
|---|---|
| Bevy test / staging sandbox | https://<instance-id>-staging.bevylabs.com/accounts/google/login/callback/ |
| Onboarding instance | https://<instance-id>.bevylabs.com/accounts/google/login/callback/ |
| Production community domain | https://<your-community-domain>/accounts/google/login/callback/ |
<instance-id> is the same ID used in your *.bevylabs.com subdomain. If you are unsure what it is, ask your Bevy contact or Bevy Support. <your-community-domain> is the final hostname members use when the community is live.
Important: A missing trailing slash, the wrong provider path (for example /accounts/oauth/…), or an origin that includes a path will fail Google’s redirect check with a redirect_uri_mismatch error. Google may take a few minutes after you save before the new URIs work.
Tip: If Bevy only asks you to enable Google on production first, start with the production origin and redirect URI. Add staging or onboarding rows when Bevy requests them.
What to share with Bevy
Create the client, then copy these values and send them over a secure channel to your Bevy onboarding contact or Bevy Support:
| Item | Required? | What Bevy uses it for |
|---|---|---|
| Client ID | Required | Identifies your Web application OAuth client to Google. |
| Client secret | Required | Authenticates the Bevy application to Google. Share only over a secure channel. |
| Hostnames you whitelisted | Recommended | Confirm which environments (staging, onboarding, production) already have matching origins and redirect URIs. |
Important: Google may show the Client secret only when you create the OAuth client (or when you reset the secret). Copy it immediately and store it somewhere safe before you close the dialog. Bevy configures Google on the community side — admins do not paste the secret into a public community settings screen.
After Bevy enables Google
- A Google button appears on the community login and signup pages (placement relative to the email form follows your community’s login settings).
- Members authenticate at Google, then return to Bevy on
/accounts/google/login/callback/. - Password resets for a Google sign-in path belong in the member’s Google Account — not on Bevy’s Reset password page.
Note: Bevy requests Google’s profile and email scopes so it can create or match the community account. If login fails after enablement, confirm the Client ID, secret, and redirect URI with Bevy Support before changing other Google Auth Platform settings.