> For the complete documentation index, see [llms.txt](https://docs.authgear.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.authgear.com/authentication-and-access/social-enterprise-login-providers/social-login-providers/google.md).
# Connect Apps to Google
## Set up OAuth client on Google Cloud Platform
To configure Google OAuth client for Authgear, you will need to create an OAuth client on Google Cloud Platform first.
### Create a new project
Create a project on Google Cloud Platform through [console](https://console.cloud.google.com/). If you are adding Authgear to your existing Google Cloud Platform projects, you may skip to the next step to create the OAuth client.
### Create OAuth Consent Screen
After creating a new project, you will need to configure the OAuth consent screen. Press the 
button on the top-left and go to **APIs & Services** -> **OAuth consent screen** and follow the instruction to create the consent screen.
### Create OAuth client ID
1. Go to -> **APIs & services** -> **Credentials**
2. Click **Create Credentials** -> **OAuth client ID**
3. Choose **Web application** in **Application type** and assign a name as reference. You should *always choose Web application* here regardless of the platform of the app you are creating. It is because this OAuth Client ID is used by your Authgear services, which is a web application in Google’s classification.
4. In **Authorized JavaScript origins**, add your Authgear endpoint, e.g. `https://myproject.authgear.cloud`
5. In **Authorized redirect URIs**, add `https:///sso/oauth2/callback/google`. For example, `https://myproject.authgear.cloud/sso/oauth2/callback/google`
6. After creating a client ID, you will see the client ID under the **OAuth 2.0 Client IDs** section of the **Credentials** page.
{% hint style="info" %}
Redirect URI has the form of `/sso/oauth2/callback/:oauth_provider_alias`. The `oauth_provider_alias` is the OAuth Provider Alias configured for this provider in Authgear Portal.
{% endhint %}
You can find more details in [official Google Cloud Platform doc](https://support.google.com/cloud/answer/6158849)
## Configure Sign in with Google in Authgear Portal
### Get your OAuth Client details
After creating an OAuth client, click the name of OAuth client to view the details.
You will need the values of **Client ID**, **Client secret** to configure Google Sign In.
### Configure in Authgear Portal
1. In the portal, go to **Authentication > Social / Enterprise Login**.
2. Enable **Sign in with Google**.
3. Fill in the **Client ID** and **Client Secret** with the values obtained from the previous step.
4. **Save** the settings.
🎉Done! You have just added Google Sign In to your apps!
Your end-users can now sign in with Google on Authgear pre-built Log In and Sign Up page. Existing end-users can connect their account to Google in the [User Settings](/customization/built-in-ui/user-settings.md) page.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.authgear.com/authentication-and-access/social-enterprise-login-providers/social-login-providers/google.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.