# Google Sign-in configuration
Use this when you want to enable the **Google** button in an enrolment form.
Start with [Social sign-in](https://docs.thewalletcrew.io/enroll/enrolment-form/social-sign-in) to understand the user flow. Then come back here for the provider setup.
Connect with Google in an enrolment form example
### Overview
#### What you’ll set up
* A **Google OAuth 2.0 Client ID**.
* **Authorized JavaScript origins** for your enrolment form domains.
* The Client ID stored in **The Wallet Crew** admin console.
#### Prerequisites
* Access to your brand’s **Google Cloud Console** project.
* Permission to create **OAuth 2.0 Client IDs**.
* The list of domains where your enrolment forms will run (prod + staging + dev + custom).
### Configure Sign in with Google
{% stepper %}
{% step %}
#### **Open Credentials**
Open the Google Cloud Console **Credentials** page:
{% endstep %}
{% step %}
#### **Create a Web application OAuth client**
1. Click `Create credentials` → `OAuth client ID`.
2. Choose application type: `Web application`.
3. Set a name. Example: `neostore login`.
{% endstep %}
{% step %}
#### **Configure origins**
Add **Authorized JavaScript origins** for every domain you will use.
* `https://app.neostore.cloud`
* `https://app-qa.neostore.cloud`
* `https://app-dev.neostore.cloud`
* Any **custom domain** you use for enrolment forms (add the exact origin).
Leave **Authorized redirect URIs** empty.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
Google Sign-In for web uses the **Client ID**. It’s safe to paste it in the admin console.
Do not share any Google **client secret**. You should not need one for this flow.
{% endhint %}
### Configure Google in The Wallet Crew
1. Open **Social logins → Google** in the admin console.
The Wallet Crew - Google Social Sign In configuration
2. Paste the **Client ID** from Google.
3. Save.
### Enable Google on your enrolment form
Enable the provider in the enrolment form settings.
Go into `advanced configuration -> Layout` Open the layout you want to activate social sign-in on and add these lines
```yaml
signinOptions:
providers:
- type: android
displayProps:
isMobile: true
isAndroid: true
```
For more information see [Enrolment form](https://docs.thewalletcrew.io/enroll/enrolment-form).
### FAQ
Do we need a Google client secret?
No. This setup uses the **Google Client ID** only.
If you see a client secret in Google Cloud Console, don’t paste it anywhere in Wallet Crew.
Should we configure “Authorized redirect URIs” in Google?
No. Leave **Authorized redirect URIs** empty for this flow.
If you add redirect URIs, it usually doesn’t help. It can also confuse debugging later.
What exactly must be added as an “Authorized JavaScript origin”?
Add the **origin only**: `scheme://host` (and port if you use one).
Examples:
* ✅ `https://app.neostore.cloud`
* ✅ `https://brand.example.com`
* ❌ `https://app.neostore.cloud/molia/mobile` (paths are not allowed)
We use a custom domain. What should we do?
Add your custom domain as an **Authorized JavaScript origin** in Google Cloud Console.
Use the exact domain users see in the browser. Example: `https://wallet.brand.com`.
Why do we list prod, QA, and dev origins?
Google validates the origin at runtime.
If a user hits QA but only prod is configured, Google rejects the sign-in.
Where do we enable the Google button in the user journey?
Provider setup is not enough. You must also enable Google on the enrolment form.
See [Social sign-in](https://docs.thewalletcrew.io/enroll/enrolment-form/social-sign-in) and [Enrolment form](https://docs.thewalletcrew.io/enroll/enrolment-form).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.thewalletcrew.io/enroll/enrolment-form/social-sign-in/google-sign-in.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
