Docs
Home

Connecting Google Drive

Connect Google Drive so Monad can search, read, copy, and create files on your behalf.

Connect Google Drive and Monad can work with your files for you — without ever handling your password. You connect once with your own Google sign-in, and agents use that access when they act on your behalf. While the connection is active, Library also maintains a read-only mirror of supported files so related clusters stay current.

Google Drive connects directly to Google, so Monad can search and read your files, see who they're shared with, and copy or create files.

What Google will ask for. When you connect, Google's consent screen lists the access you're granting — reading the files you can already see, and creating or copying files. Agents only ever work with files you can already access; if you only want agents to read, you can turn off the create/copy tools per connector after connecting (see Choosing what agents can do).

Connecting

There's nothing to set up — Monad handles the Google connection for you, so you never create an OAuth app or paste any keys.

  1. Open Settings → Connection Preferences (or the Connectors section on the Connections page) and find Google Drive.
  2. Click Add, then on the connector's page click Connect.
  3. Sign in with Google and approve the requested access. You'll be returned to Monad with a green Connected badge.

Once Google Drive is connected, its card turns into a dimmed Added tile and it shows up in your Connections list above — open it from there any time to manage or disconnect it.

From then on you can ask an agent things like "find my Q3 planning doc" or "summarize the latest file in my Reports folder" without thinking about credentials.

What Monad can do

Monad acts as your account. It can:

  • Search your files and list recently-changed ones.
  • Read a file's contents, metadata, and who it's shared with.
  • Copy an existing file, and create new files.

Agents only ever see files you can already access, and only ever touch Google Drive — never anywhere else in your account.

Choosing what agents can do

Every Drive tool can be turned off independently from the connector's page, so you can keep the connection but narrow what agents may do — for example, allow searching and reading but block creating or copying files. Turning a tool off here disables it for agents; it doesn't change the access you granted Google (that only changes when you reconnect or disconnect). Read-only tools appear first, followed by tools that can change Drive; each group is alphabetical. A writes badge beside a tool's name marks the second group. These switches control agent tools. They do not pause Library's read-only mirror; disconnect Drive to stop both uses of the connection.

How Drive appears in Library

A personal Drive connection creates Only you Library objects. A shared workspace connection creates workspace-visible objects. Library keeps metadata and supported extracted content current and may use them in eligible clusters.

You can promote an eligible object from a personal connection without sharing your whole Drive: open the object's Monad detail page and choose Share to workspace. The action is recorded, and that object can then contribute to workspace clusters. Choose Revoke share to return it to Only you; Library removes its workspace memberships and grounded claims as it rebuilds the affected clusters. Sharing through Library does not change the file's Google Drive permissions.

Reconnecting

If you see an amber Reconnect needed badge, your access expired or the permissions changed. Click Reconnect and approve again, or choose Disconnect to remove your connection without reconnecting first.

Disconnecting

Click Disconnect at any time and Monad immediately stops using your Google Drive account. Disconnecting also revokes Monad's access at Google, so it's removed from your Google Apps with access to your account list — you don't need to do that step yourself. Library removes the connection's mirrored objects and refreshes affected clusters. For a personal connection, other members and admins see only objects you explicitly shared—not the rest of your files or your tokens.