> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/integrations/single-sign-on/google-sso-setup.md).

# Google SSO Setup

This guide covers setting up Single Sign-On (SSO) with Google for Welkin Health. Once configured, care team members can log in to Welkin using their Google account.

> **Note:** While setting up this configuration, it is best to have two browser tabs open — one with Welkin Admin and one with Google Cloud.

## Prerequisites

* A Google Cloud account (existing or new). Use your company domain's Admin account if available.
* Welkin Admin portal access
* A Welkin user account with a Google email address already created

## Step 1: Create a user and enable SSO in Welkin Admin

1. In Welkin Admin, create a user with a Google account email address (or use an existing one)
2. Turn on **Single Sign-On** for that user from the user profile settings
3. In Admin, go to **Security Settings** → turn on Single Sign-On (Status = Active) → select **Google** as the Provider type

## Step 2: Set up a project in Google Cloud

1. Go to [console.cloud.google.com](https://console.cloud.google.com/) and sign in
2. Click **Agree and Continue**
3. Select a project → **New Project** → enter a project name, leave Location as "No Organization" → click **Create**
4. Wait for the project to be created and click **Select Project**

## Step 3: Configure OAuth consent screen

1. Navigate to **API and Services → Credentials**
2. Click **Configure Consent Screen**
3. Select User Type **External** (or **Internal** to limit to users in your organization) → click **Create**
4. Fill in your **App name** and **User support email**
5. Scroll to **Authorized domains** → click **Add Domain**
6. In Welkin Admin → Security Settings → click **Instructions** → copy the **Authorized Domain**
7. Paste the domain into Google Cloud → fill in developer contact information → click **Save and Continue**
8. Skip the Scopes tab → click **Save and Continue**
9. Under **Test users**, click **Add users** → add the user created in Step 1 → click **Add** → **Save and Continue**
10. Click **Back to Dashboard**

## Step 4: Create OAuth credentials

1. Go to **Credentials → Create Credentials → OAuth Client ID**
2. Select **Web application** → enter any name → click **Add URI**
3. In Welkin Admin → Security Settings → Instructions → copy **Authorized JavaScript origin** → paste into Google Cloud
4. In Welkin Admin → copy **Authorized redirect URI** → **change `saml2` to `oauth2` in the URL** → paste into Google Cloud
5. Click **Create**
6. Copy the **Client ID** and **Client Secret** from Google Cloud

## Step 5: Save credentials in Welkin Admin

1. In Welkin Admin → Security Settings → SSO settings → paste the **Client ID** and **Client Secret**
2. Click **Save**

## Step 6: Test

Click **Log in with Google** → select the test account → confirm login is successful.

***

More Questions? Contact <csm@welkinhealth.com> or your Implementation/CSM directly.


---

# 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.welkinhealth.com/integrations/single-sign-on/google-sso-setup.md?ask=<question>&goal=<user_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.