Drive Sync
Overview
Connect your Google Drive to GrooveOS and your team's documents become part of your shared memory — automatically, without copy-pasting. When a file is updated in Drive, GrooveOS syncs it within seconds.
Drive Sync is available on the Team plan and above. Once set up by an admin, the sync runs continuously in the background — your team never needs to think about it.
How it works
- You map a Drive folder to a project in GrooveOS settings.
- GrooveOS monitors that folder for changes via Google Push Notifications.
- When a file is added or updated, GrooveOS extracts its content and indexes it as a memory item with
truth_level=WORKING. - The document is immediately searchable by your team and your AI.
Drive folder updated
│
▼ (within seconds)
GrooveOS detects change
│
▼
Content extracted + indexed
truth_level = WORKING
team_scope = your team
project_scope = your project
│
▼
Searchable immediately
Documents synced from Drive start at truth_level=WORKING. Your team can
promote important facts to VALIDATED or CANONICAL through
the memory interface. See Memory & Knowledge for the
full truth-level guide.
Setting up Drive Sync (admin only)
Drive Sync requires an admin to authorize GrooveOS's access to your team's Google account. Non-admin members benefit from the sync automatically once it is configured.
Step 1 — Authorize Drive access
Go to team Settings → Integrations → Google Drive → Connect. This redirects to Google's authorization page. Sign in with the Google account that has access to your Drive folders.
Permissions
GrooveOS requests read access to Drive (and write access if you want the AI to write back to Drive). You can revoke access at any time from Settings → Integrations. GrooveOS never stores your Drive credentials — it uses OAuth tokens that you can revoke from your Google account.
Step 2 — Map a folder
After authorization, go to Settings → Drive → Add folder mapping:
- Select a folder from your Drive
- Choose the project scope (which GrooveOS project it maps to)
- Set the visibility (
teamorproject) - Click Save
GrooveOS immediately starts syncing the folder's existing contents, then watches for changes.
Step 3 — Multiple folders
You can map multiple Drive folders to different projects. Each folder's files are tagged
with their respective project_scope automatically:
| Drive folder | GrooveOS project | Visibility |
|---|---|---|
| /Fundraising Docs | fundraising | team |
| /Engineering / RFCs | engineering | project |
| /Team / Meeting Notes | general | team |
Files in each folder are tagged with their respective project_scope automatically.
Supported file types
| File type | How it's processed |
|---|---|
| Google Docs | Exported as plain text and indexed |
| Google Sheets | First sheet exported as text |
| Text extracted and indexed | |
| Markdown (.md) | Indexed directly |
| Text files (.txt) | Indexed directly |
| Images | Not indexed (coming soon) |
Large files
Files larger than 10 MB are chunked automatically. Long documents are split into overlapping segments so semantic search can pinpoint specific sections. The full document is still attributed to a single memory item.
AI-powered Drive access (MCP Tool)
With the Team plan, your AI can also read and write Drive files on demand during a chat — not just at sync time. When your AI needs to check a specific document, update a sheet, or create a new file, it can do so directly through GrooveOS's MCP integration.
See MCP Tools → Google Drive for setup and available commands.
What's next
- Memory & Knowledge — Promote Drive docs to CANONICAL so your AI always has them in context.
- MCP Tools — Let your AI read and write Drive files on demand.
- API Reference — Query Drive-synced memory items programmatically.