> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/textual-install-administer/user-access-textual/textual-sso/textual-sso-google.md).
# Google
Use these instructions to set up Google as your SSO provider for Tonic Textual.
## **Create an OAuth 2.0 client ID in Google**
1. Go to
2. Click **Create credentials**, located near the top.
3. Select **OAuth client ID**.
4. Select **Web application** as the application type.
5. Choose a name.
6. Under **Authorized redirect URIs**, add the URL of the Textual server with the endpoint `/sso/callback/google`.\
\
For example, a local Textual server at `http://localhost:3000` would need `http://localhost:3000/sso/callback/google` to be set as the redirect URI.\
\
Also note that internal URLs might not work.
7. On the confirmation page, note the client ID and client secret. You will need to provide them to Textual.
## **Textual configuration**
After you complete the configuration in Google, you uncomment and configure the required [environment variables](/textual/textual-install-administer/configuring-textual/textual-env-var-configure.md) in Textual.
* The client ID
* The client secret
For Kubernetes, in **values.yaml**:
```
# Google SSO Config
# -----------------
#googleClientId:
#googleClientSecret:
#googleGroupFilterRegex:
```
For Docker, in **.env**:
```
#SOLAR_SSO_GOOGLE_CLIENT_ID=#
#SOLAR_SSO_GOOGLE_CLIENT_SECRET=#
#SOLAR_SSO_GOOGLE_GROUP_FILTER_REGEX=#
```
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tonic.ai/textual/textual-install-administer/user-access-textual/textual-sso/textual-sso-google.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.