Google Drive
A Drive holds everything the company ever wrote. And nobody reopens a document from March.
What it changes
Your documents are not short on information, they are short on recall. The note explaining why you ruled out that vendor exists. It sits in a folder next to two hundred others, and it will never surface on its own.
Verbasil reads those documents once, pulls out what commits the company, and takes care of handing it back when the question returns.
What enters the memory
Only the files you choose in Google's picker. That is a difference in kind, not in degree: Verbasil asks for access to the files you point at, not to your Drive. The rest is invisible to it.
Text documents, PDFs, exported meeting notes, proposals: anything made of sentences.
What Verbasil does with it
- Decisions the document settles, with their reasoning.
- Commitments made to a customer, and the date when there is one.
- Learnings, including the ones you would rather forget.
- Recurrences across documents: the same remark in three different proposals becomes a signal, not a coincidence.
Every item stays tied to the file and the exact passage. You click, you reread, you judge.
How to connect it
- Open Integrations in Verbasil, then Google Drive.
- Connect your Google account.
- Select files in Google's picker, one by one or in batches.
- Review what Verbasil proposes in Sources, then approve.
What it does not do
Verbasil does not crawl your Drive and does not index it. It cannot: the permission it asks for does not allow it.
It writes nothing to Drive, and moves no files.
FAQ
Does Verbasil have access to my whole Drive?
No. The permission requested covers only the files you point at yourself. That is a technical limit, not a promise.
Are files copied somewhere?
The extracted text enters your memory, with its link back. It is never used to train a model.
What about files shared with me?
They work like your own, as long as you can open them.