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

# Connect Google Drive Individual

> Connect one Google user's Drive files through Google's hosted integration endpoint.

Google Drive Individual is a **Dev Testing** integration. Use it when one signed-in Google user should grant daoco access only to Drive files available to that user during provider approval or testing. Google hosts the [MCP](/connections/integrations#what-is-mcp) endpoint for this connection.

## Connect Google Drive Individual

<Steps>
  <Step title="Enable Dev Testing">
    A workspace owner or admin must enable **Dev Testing** integrations in **Settings** -> **Preview features**.
  </Step>

  <Step title="Open the Google Drive Individual card">
    Open **Connections** -> **Integrations** -> **Dev Testing** and choose **Google Drive Individual**.
  </Step>

  <Step title="Approve Google OAuth">
    Choose **Connect**, sign in with the Google user, and approve Drive read and file scopes.
  </Step>

  <Step title="Verify safely">
    Confirm the row is healthy, then run a minimal read-only [`/integration`](/connections/integrations#what-is-mcp) proof. Do not prove access by showing file contents, file IDs, private names, or folder details.
  </Step>
</Steps>

## Workspace restrictions

If the Google account belongs to a restricted Workspace, a Google Workspace admin may need to trust the daoco OAuth app or allow these scopes:

```text theme={null}
https://www.googleapis.com/auth/drive.readonly
https://www.googleapis.com/auth/drive.file
```

daoco Google OAuth client ID:

```text theme={null}
96740286304-9cfdidtfpagihnu2i2dmkk9is3ann2mr.apps.googleusercontent.com
```

<Warning>
  This guide remains available for testing, but Google Drive Individual is not part of the normal Files & Docs production category.
</Warning>