Google Drive

Connect Google Drive with the drive.file scope only. Your agents can open Google's own Picker so you choose each file yourself - they can never browse your Drive.

Esta página aún no está disponible en tu idioma, mostramos la versión en inglés.

Connect Google Drive and your agents can pull a file into their work, save what they produce back into your Drive, and update it later - without ever being able to look through your Drive.

That last part is the whole design. Unyo asks Google for one permission: drive.file. It grants per-file access, file by file, only to files you hand over through Google's own Picker, plus files Unyo created itself. There is no scope in the request that would let an agent list, search or open anything else.

Unyo cannot browse your Drive

We request drive.file and nothing else. An agent can only touch a file if you picked it in Google's Picker in this conversation, or if Unyo created it. Everything else in your Drive is invisible to us - not by policy, by scope. We retired the broader drive.readonly scope on 30 April 2026 and replaced it with the Picker.

What it unlocks

Once Drive is connected, these become available to your agents:

What you ask	What happens
Pick a file by describing it	Say "attach my Q2 invoice" and Google's official Picker opens with "Q2 invoice" already typed into its search box. You click the file. Only then does the agent get its ID.
Read a file	The agent reads the text of a file you picked (or one it created) and works from the real content instead of guessing.
Save its work to Drive	Any agent can create a real Google Doc from what it just wrote - filed automatically, stamped with your brand.
Update a file it created	Ask for a change and the agent reads the current version first, then edits only the part you asked about.

Per agent

Maya (email) - attaches Drive files to an email. Ask for "the Acme contract" and the Picker opens pre-filtered; you pick, she attaches. Up to 10 attachments per message.
Lucy (content) - exports a finished document straight out of Unyo as a real Google Doc in your Drive, not a copy-paste.
Blake (data) - the spreadsheet panel exports a workbook to Drive or Google Sheets in one click.
Every other agent - Ashley, Alex, Riley, Tyron, Sam and Ema can all read a picked file and save their output back to Drive.
Steve (websites) - deliberately cannot. Drive tools are stripped from Steve's toolbox entirely. He builds sites; he has no business in your files.

The Picker is the permission

drive.open_picker never returns a file ID on its own. It opens the Picker in your browser and stops. The agent's turn pauses until you've chosen. The file IDs come back from you, not from a search the agent ran.

Auto-filing, and a document that looks like yours

When an agent saves to Drive, it doesn't dump a file in the root. It creates the folder path:

/Unyo/{Agent}/{YYYY-MM-DD}/

So Maya's Tuesday output lands in /Unyo/Maya/2026-07-16/, Blake's in /Unyo/Blake/2026-07-16/. Each agent gets its own subfolder, each day its own dated folder. Six months in, your Drive is still navigable.

Each saved document is formatted on the way out:

a centred title,
a dateline reading "Created by {Agent} via Unyo",
your markdown rendered as real styled HTML - headings, tables, lists,
a footer rule,
and your brand logo at the bottom, pulled from your Brand Kit in the Neural Core.

Set your logo once in the Neural Core and every document any agent files to Drive carries it.

How to connect

Open Integrations from the sidebar. (It's a top-level page - not inside Settings.)
Find the Google Drive card and click Connect.
Sign in with your Google account.
Google shows you one permission: see, edit, create and delete only the specific Google Drive files you use with this app. Approve it.
You land back on Integrations and the card shows the connected Google account.

Connecting Drive won't widen Gmail or Calendar

Each Google service is consented separately - we send include_granted_scopes=false. Connecting Drive adds drive.file and nothing else. Your Gmail and Calendar permissions are untouched, and there's no quiet accretion of scopes over time.

If an agent needs Drive mid-conversation and you haven't connected it, it doesn't fail. The run pauses on a "Waiting for connection" notice, hands you a Connect button, and once you're back it replays the exact action it was about to do - no retyping.

Permissions

One scope. Here's the whole request:

Scope	What it lets your agents do, in plain English
`drive.file`	Open, read, update and create only the files you picked in Google's Picker, plus files Unyo created itself. Per-file. Nothing else in your Drive is reachable.

Scopes we deliberately do not request

Scope	Why we don't ask for it
`drive.readonly`	Read every file in your Drive. We used to request this. We retired it on 30 April 2026 and rebuilt the feature around the Picker instead. The capability is gone, not just unused.
`drive` (full)	Full read/write over your entire Drive, including deleting files we never created. Never requested.
`drive.metadata.readonly`	Enumerate the names and structure of every file you own. Never requested - it would let us map your Drive without reading it, which is exactly what the Picker design exists to prevent.

The pattern holds elsewhere: gmail.send dropped because gmail.modify already covers it, two Instagram scopes and three Facebook scopes omitted as unused. Nine Google scopes became five.

If you connected Drive before 30 April 2026

Your grant still carries the old, broader drive.readonly permission until you act - Google doesn't shrink a grant retroactively, and we can't do it for you. Disconnect and reconnect Drive to drop to drive.file only. Nothing breaks in the meantime; you're just holding a wider permission than we now ask for.

What Unyo does with your data

Your tokens are encrypted at rest. Drive tokens live in google_service_connections and are written and read only through SECURITY DEFINER database functions that encrypt and decrypt them. No code path reads a token column directly. As of 16 July 2026, all 17 populated OAuth token columns across the platform were verified AES-256 encrypted at the cipher-byte level - zero plaintext tokens exist.
Tokens never appear anywhere you could leak them. Not in a log, not in an error message, not in a tool result, not in an SSE stream, not in a queued job payload. A token is resolved for the duration of one outbound call to Google and discarded.
Your file content is never used to train a model. Every model Unyo runs is under a no-training, zero-retention guarantee. Your file content is used to answer the request you made, and nothing else.
Your rows are yours. Row-level security is on every user-scoped table - 109 of 109 public tables, 291 policies, verified live on 16 July 2026 - keyed to your user ID.
Drive file contents never enter the code sandbox. Blake's Python sandbox has no internet and no secrets, and Google user data is barred from it by a hard gate.
No per-file charge. Picking, reading, saving and updating Drive files carry no tool cost. You're billed for the model's real token usage on the run.

Try it

Attach my Q2 invoice to an email to accounting and ask them to process it this week.

Read the Acme contract I'm about to pick and tell me what the termination clause actually says.

Save this as a Google Doc in my Drive called "Q3 content plan".

Open the strategy doc I picked, then update the timeline section to push everything back two weeks.

Export this spreadsheet to Google Sheets.

FAQ

Can Unyo see files I haven't picked?

No - and not as a promise, as a technical limit. We hold the drive.file scope, which Google enforces on its own side: it grants access per file, only to files you selected through the Picker or that our app created. A request for any other file ID is rejected by Google, not by us. There is no "browse my Drive" or "search my Drive" tool in Unyo, because there's no scope that would make one work.

What happened to drive.readonly?

We retired it on 30 April 2026 and rebuilt the whole feature around Google's official Picker. drive.readonly would have let us read every file you own - far more than we need to attach an invoice to an email. The narrower drive.file plus a Picker click does the same job with a fraction of the exposure. If you connected before that date, disconnect and reconnect to drop the old scope.

Does disconnecting Drive revoke Unyo's access at Google?

Honest answer: no, not on its own. Gmail, Drive and Calendar share a single Google grant. If we called Google's revoke endpoint when you disconnect Drive, it would kill the entire grant and silently break your still-connected Gmail and Calendar. So Disconnect deletes the connection on our side - we stop having a usable connection, and no agent can reach your files.

To revoke the grant at Google itself, go to myaccount.google.com/permissions and remove Unyo. Deleting your Unyo account does revoke it for you - there, killing the whole grant is exactly right.

Which agents can touch my Drive?

All of them except Steve - Ashley, Maya, Alex, Riley, Tyron, Sam, Lucy, Blake and Ema. Steve, the website builder, has every Drive tool stripped from his toolbox, along with Calendar. Each agent's toolbox is a runtime access control, not a prompt instruction: a tool Steve isn't allowed to use is never loaded into his session, so there's nothing for him to call.

Where do saved files end up?

In /Unyo/{Agent}/{date}/ - for example /Unyo/Maya/2026-07-16/. The folder hierarchy is created for you on the first save. Each document gets a title, a "Created by {Agent} via Unyo" dateline, a footer, and your brand logo from the Neural Core.

Can an agent overwrite one of my existing files by mistake?

It can only update files it can reach - files you picked or files Unyo created. And before updating, it's required to read the current content first and change only the part you asked about. New documents always go to a fresh file in the dated Unyo folder; drive.save creates, it never overwrites.

Troubleshooting

The Picker didn't open. It's a popup from Google. Allow popups for unyo.app and ask again.

"Drive connection expired" or the agent asks you to reconnect. Google invalidated the token out of band - an account password change, or access removed from your Google security settings. Unyo detects this, marks the connection dead rather than failing silently, and tells you in your own language. Reconnect from Integrations and carry on.

The agent says it can't read a file. Almost always the drive.file boundary doing its job: the file wasn't picked in this conversation and wasn't created by Unyo. Ask for it again and pick it in the Picker.

You picked the wrong file. Just say so and ask again - the Picker reopens and the new pick supersedes the old one.

You want the agent to pick several files at once. Say so explicitly - "attach all my Q2 invoices", "the last 3 contracts", "the contract and the brief". Plural or counted phrasing switches the Picker to multi-select. Otherwise it's a single pick.

Drive is connected but the agent doesn't seem to have it. Check you're not talking to Steve - he has no Drive tools by design. Any other agent will.