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 endpoint for this connection.
Connect Google Drive Individual
Enable Dev Testing
A workspace owner or admin must enable Dev Testing integrations in Settings -> Preview features.
Open the Google Drive Individual card
Open Connections -> Integrations -> Dev Testing and choose Google Drive Individual.
Approve Google OAuth
Choose Connect, sign in with the Google user, and approve the Drive read, file, and Google Docs scopes.
Verify safely
Confirm the row is healthy, then run a minimal read-only /integration proof. Do not prove access by showing file contents, file IDs, private names, or folder details. What the connection can do
The assistant can search, read, and download files, create new files (text content is converted to a Google Doc by default), copy files, and edit an existing Google Doc in place by appending paragraphs or replacing exact text. Creates, copies, and edits wait for your approval in chat. In-place editing needs the Google Docs scope: connections made before it was added keep working for reads, and the assistant will ask you to reconnect Google Drive before its first edit.
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:
daoco Google OAuth client ID:
This guide remains available for testing, but Google Drive Individual is not part of the normal Files & Docs production category.
