> ## Documentation Index
> Fetch the complete documentation index at: https://ona.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Google

You can set up Single Sign-on (SSO) with Google for your team.

This page helps you create the Google OAuth/OIDC application Ona needs. You will use the resulting **Client ID**, **Client Secret**, and **Issuer URL** in Ona. For the full organization-side setup, see [Single sign-on (SSO)](/ona/sso/overview).

## Prerequisites

* access to create new [API Credentials](https://console.cloud.google.com/apis/credentials) in your Google Cloud project
* admin access to your Ona organization login settings

## Create an OAuth/OIDC application

The OAuth/OIDC application allows you to integrate with Ona.

1. Navigate to your *Google Cloud Console > API Credentials*.

2. Select **Create Credentials**, and choose **OAuth Client ID**.

3. Configure your *OAuth Client ID* by pasting the **Callback URL** shown in Ona into Google's **Authorized redirect URI** field.

4. Obtain the *Client ID* & *Client Secret* and input these into your Ona Setup page.

5. Use Google's global *Issuer URL*: `https://accounts.google.com`

6. Continue with the SSO configuration in Ona and use **Save & Test** to verify the login flow

## Values to enter in Ona

When you return to Ona, enter:

* **Client ID** from Google
* **Client Secret** from Google
* **Issuer URL**: `https://accounts.google.com`

Then test the configuration before rolling it out to your team.

## Google-specific notes

* Copy the redirect URI from Ona rather than retyping it. This avoids callback mismatches.
* If you use domain-based login in Ona, make sure the relevant email domain is also verified and associated with the Google login provider in Ona.
* If testing fails, the most common cause is an incorrect redirect URI or a mismatch between the Google app and the provider configuration in Ona.

## Next steps

* [Single sign-on (SSO)](/ona/sso/overview)
* [SCIM Provisioning](/ona/scim/overview)
