Skip to main content
Drive is gated during private beta. Google requires app verification for restricted scopes like drive.readonly, and verification takes 4–6 weeks. While Repo waits, Drive access is per-customer manual approval. Click Request access on the Drive connector card → we’ll email you when you’re added as a Google Cloud test user (usually within 24h) → then Connect works as normal.

​
What’s ingested

  • Google Docs (full text, headings preserved)
  • Google Sheets (cell content, sheet names)
  • Markdown files
  • CSV files (rows up to a token cap)
  • PDF files (text extraction)
  • File metadata (owner, last modified, sharing settings, folder path)

​
What’s NOT ingested

  • Files in Shared Drives where the connecting user is not a member
  • Files explicitly excluded by mime type (videos, images, executables)
  • Trashed files
  • Comments and suggestions (only the document body)

​
OAuth scopes

  • https://www.googleapis.com/auth/drive.readonly (restricted — requires Google verification for production)
  • https://www.googleapis.com/auth/userinfo.email (to identify the connecting account)
  • https://www.googleapis.com/auth/userinfo.profile

​
Access policy preservation

Drive is the only connector that preserves per-file ACLs. Every ingested file carries an accessPolicy block describing:
  • Who has direct access (emails)
  • Domain-wide sharing settings
  • “Anyone with the link” status
This metadata is returned in retrieval hits so your agent (or downstream re-enforcement) can filter results by the requesting user’s identity.

​
Backfill warning

Older Repo deployments ingested Drive files before access policy preservation shipped. The connector card surfaces a warning when this is the case:
Access-policy backfill required: N Drive items are excluded from retrieval until a full resync preserves sharing metadata.
Run a fullResync to backfill — it re-fetches every file’s sharing settings and updates the access policy.

​
Sync cadence

Auto-sync every 15 minutes. Uses Drive’s change-feed API for incremental syncs; full resyncs walk the entire folder tree.

​
Limitations during gated beta

  • Google’s “unverified app” warning screen appears for end users until Google verification completes. They click “Advanced → Go to Repo (unsafe)” to proceed. We know it’s ugly — verification is in progress.
  • Hard cap of 100 test users per Google Cloud OAuth client during verification. If you need to onboard more before verification clears, contact us.
  • Verification ETA: 4–6 weeks from submission. Submitted: 2026-05-24.