> For the complete documentation index, see [llms.txt](https://docs.chord.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chord.co/chord-oms/developer-tools/authentication/chord-platform-and-google-oauth-integration.md).

# Chord Platform and Google OAuth Integration

### Introduction

Users can now log into Chord's platform with Google OAuth using their company's corporate accounts. This will serve as an additional option to log into the platform alongside the pre-existing Magic Link login method.

This experience provides a seamless, secure, and intuitive way of logging into the Chord platform for customers who already use corporate Google accounts.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-71fa7e4e5c446e8b38fa321f9f8f540e00e60a0a%2Fchord-platform-and-google-oauth-integration-1.png?alt=media)

When the user clicks on the ‘**Continue with Google**’ button they will be redirected to authenticate with Google, which will present them with Chord’s Google OAuth Client.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-04f2dfd001d9b553ea5702865be9e11cfc9844b1%2Fchord-platform-and-google-oauth-integration-2.png?alt=media)

If the user has enabled passkey or an extra authentication step on their Google account, Google will ask them to provide extra verification for example passkey or an authorization code.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-b6ce62157593dc10a572757809ba4a04f45da5a1%2Fchord-platform-and-google-oauth-integration-3.png?alt=media)

If the user has not enabled any extra security features on their account, they will be asked to provide their password.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-d8568ed2128130607a9c9f2fb42839af1688b560%2Fchord-platform-and-google-oauth-integration-4.png?alt=media)

If login is successful, the user will be presented with their landing page.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-0ef1cdc97d4ec2c1bef4b44ce9ff0acef2307c86%2Fchord-platform-and-google-oauth-integration-5.png?alt=media)

If login is not successful, the user will be redirected to the login page.

![](https://3559351341-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGejRW1RLC9yasX56Xzxu%2Fuploads%2Fgit-blob-71fa7e4e5c446e8b38fa321f9f8f540e00e60a0a%2Fchord-platform-and-google-oauth-integration-1.png?alt=media)

### Accessibility terms

Not every member of your company's Google workspace will automatically have access to the Chord platform. **Existing** users of the Chord platform within your company will have access but before a **new** user can log into the Chord platform using Goole OAuth, the user will need to be invited into your company's Hub workspace by an existing member of your company's workspace.


---

# 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.chord.co/chord-oms/developer-tools/authentication/chord-platform-and-google-oauth-integration.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.