> ## 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

> Connect one Google account's Drive so daoco can find and read files and Google Docs, and create files with your approval.

Google Drive is an **Available** Files & Docs integration. It connects through [Composio](https://composio.dev), so Google's consent screen names Composio, not daoco. Composio holds the Google grant and runs each Drive request; daoco stores only a reference to the connected account.

You can connect it now from **Connections** -> **Integrations** -> **Files & Docs**. No preview opt-in or Dev Testing setting is required. Connect one account per brand; to use the same account with another brand, connect it there too.

## What daoco can do

* Find files and folders, and read file details and comments.
* Read Google Docs and sheet values, and export Docs, Sheets, and Slides as text.
* Create files from text, create folders, copy files, add comments, and replace the contents of non-Google files.

Every change asks for your approval in daoco first.

## Limits

* Existing Google Docs cannot be edited in place through this connection. Ask for a new file instead. Replacing content applies only to non-Google files and replaces the whole file.
* Sharing, moving, trashing, and deleting files are not supported.
* Access follows the connected Google account's permissions. Connecting does not give daoco access to files that account cannot open.
* This connection does not sync folders into brand sources. Import selected files during onboarding when you want a copy in your brand material.
* Google's consent requests access to all Drive files the account can access, including write and delete permissions. Daoco offers only the operations listed above, with approval before changes.

## Connect Google Drive

<Steps>
  <Step title="Open the Google Drive card">
    In daoco, open **Connections** -> **Integrations** -> **Files & Docs** and choose **Google Drive**.
  </Step>

  <Step title="Approve Google access">
    Choose **Connect**, sign in with the Google account daoco should use, and allow access on the Composio consent screen.
  </Step>

  <Step title="Verify from chat">
    Ask [`/integration`](/connections/integrations#what-is-mcp) to find your brand guidelines in Drive.
  </Step>
</Steps>

## Disconnect

Disconnect Google Drive from its card in **Connections**. daoco deletes the Composio account and its stored credentials, which ends daoco's access. The Composio app can stay listed in [your Google account's third-party connections](https://myaccount.google.com/connections). Remove it there only if no other brand or app still uses it: removing it ends Composio access for that Google account everywhere.

## Google Workspace accounts

Your Google Workspace admin may limit which third-party apps can use company accounts. If so, connecting fails until they allow Composio's app:

<Steps>
  <Step title="Open app access control">
    In the [Google Admin console](https://admin.google.com), go to **Security** -> **Access and data control** -> **API controls**, then choose **Manage Third-Party App Access**.
  </Step>

  <Step title="Find Composio">
    Choose **Configure new app**, search for **Composio**, and select the app Composio publishes.
  </Step>

  <Step title="Allow it">
    Choose who the setting applies to, set access to **Trusted**, and save. **Limited** access is not enough if your admin restricts Google Drive as a Google service. Then connect again from daoco.
  </Step>
</Steps>

Admin changes can take several minutes, and sometimes longer, to reach every account.

To connect admin-approved shared drives without each person signing in, use [Google Drive Workspace](/connections/mcp/google-drive-workspace) instead.

## Brand onboarding

This connection gives the assistant Drive tools. It does not sync Drive folders into your brand sources. During onboarding, use **Import selected files from Google Drive** to add individual files.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.