> For the complete documentation index, see [llms.txt](https://inflight.dope.security/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inflight.dope.security/dope.console/settings/users/importing-from-google.md).

# Importing from Google

When importing users & groups from Google, you will face the below error on the first-time you try to authenticate:

<figure><img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FtFkRoAYRs2sokw6q6ktZ%2Fusers-google-autherror.png?alt=media&amp;token=510a37b4-b6b5-4bcb-b904-5a0254b19f75" alt="" width="375"><figcaption></figcaption></figure>

The reason is that certain sensitive permissions are required for the import:

| Sensitivity                      | Scopes                                                                                                                                                                                                                                                                  | Why Dope Requires This                                                                                                                                                      |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Non‑sensitive** (OIDC Auth)    | `openid` `https://www.googleapis.com/auth/userinfo.profile` `https://www.googleapis.com/auth/userinfo.email`                                                                                                                                                            | Returns the user’s ID‑token + profile + primary email for identification                                                                                                    |
| **Sensitive** (User/Group Synch) | `https://www.googleapis.com/auth/admin.directory.user.readonly` `https://www.googleapis.com/auth/admin.directory.group.readonly` `https://www.googleapis.com/auth/admin.directory.group.member.readonly` `https://www.googleapis.com/auth/admin.reports.audit.readonly` | Read‑only access to users, groups, group memberships, and Admin SDK audit logs to perform regular User/Group synchronization, and process delta for groups every 15 minutes |

## To resolve this:

1. Login to [Google Admin Sconsole](https://admin.google.com/u/0/ac/owl/list?tab=configuredApps\&hl=en) as an Administrator. Navigate to Security -> Access and Data Control -> API controls, and select **MANAGE THIRD-PARTY APP ACCESS**

![API Security Controls are managed here](https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FvY2OlW1OlrpusVejPlz4%2Fusers-google-apicontrols.png?alt=media\&token=4728ecdc-73ce-4c60-b3e4-d1131ab0313d)

2. Select Configure new app\ <br>

   <figure><img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FqoRXCVFDLXxcAhMDunOV%2Fimage.png?alt=media&amp;token=c08fbfd8-f8f0-4217-9267-176e9060f006" alt=""><figcaption></figcaption></figure>
3. Search for dope.security's Client ID

`478881077855-4cs12s5t8lae8vsh43svpsahneb1fgu2.apps.googleusercontent.com`

<figure><img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2FuwMcxHCuC3sxXAtIt5yu%2Fimage.png?alt=media&amp;token=0a99702b-d98f-4a4e-b63d-cee546a7bbee" alt=""><figcaption></figcaption></figure>

3. Click the “Dope Security” app and Configure the App access to **Trusted**<br>

   <figure><img src="https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2Fyt1jdvwmsRINRi4FTjii%2Fimage.png?alt=media&amp;token=d95c8bba-3c80-47e9-8658-29e86558d9fe" alt=""><figcaption><p>Mark app as Trusted</p></figcaption></figure>
4. Once configured, you will see the app listed as Trusted in the third-party app list.

![](https://4250118259-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fqdf21diS0j19gSMF9LeP%2Fuploads%2Ff0kEidIrgwrR3bKdDDaJ%2Fusers-google-configured.png?alt=media\&token=b6f6204a-03a0-4948-a4fe-9971f9f706c5)


---

# 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://inflight.dope.security/dope.console/settings/users/importing-from-google.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.
