Skip to main content

Google Drive connector

The Google Drive integration is consent-first and folder-scoped. It is built to do the minimum required to ingest a folder of documents — nothing more.

Before binding any Drive folder, the connector asks you to grant access explicitly. Until you grant consent, the connector cannot read anything from your Drive — at all.

If you decline, the connector simply stops. The local-folder path stays available as an alternative.

Permissions​

The connector requests the minimum Google Drive scopes needed for selected-file and folder operations and basic account identity. We do not ask for broad full-drive access.

Operational rules:

  • OAuth tokens are stored server-side and never exposed to the browser.
  • Permissions are revocable from your Google account at any time.
  • The connector never escalates privileges in the background.

Folder selection​

You must point the connector at one specific folder.

  • Selecting the whole drive (root) is not allowed.
  • Once a folder is bound, the binding is stored and reused for that workspace.
  • If a binding becomes invalid (folder moved, deleted, or unshared), you reconnect and pick again.

This is deliberate. Bound-folder scope keeps the connector inside the scope your team agreed on.

Operational notes​

  • If the folder picker is blocked or unavailable, run the reconnect flow.
  • If a source reference can no longer be resolved, the document preview shows Source link unavailable.
  • Rebinding a folder restores ingestion continuity without losing the registry history that came before.