Cloud storage
What cloud storage integrations do
Cloud storage integrations bring external folders into Colabra as project evidence. They are the right choice when the deal team already receives material through an existing folder structure and wants the evidence pipeline to start without manual upload.
In practice, this is the integration families use when the seller, banker, or target team already works in a shared folder. Instead of downloading batches and re-uploading them into the project, you connect the existing source and let the evidence pipeline start from there.
All cloud storage integrations share the same operating pattern:
- connect the provider once at workspace scope
- choose the project folder from the import flow
- import the folder contents immediately
- let Colabra create new file versions when upstream files change
The seller folder becomes live evidence
Real deal example: avoid the download and re-upload loop
A sell-side team is already posting updated contracts and financial packs into a Box or Drive folder. The buy-side team connects that folder to the project once, gets the initial batch immediately, and then sees later revisions arrive as new file versions instead of as duplicate uploads scattered across email and local downloads.
Compare the providers
| Provider | Best for |
|---|---|
 Google Drive | Teams already working in Google Workspace |
 Box | Corporate M&A and diligence rooms already hosted in Box |
 Dropbox | Smaller teams and lighter file-sharing setups |
 OneDrive | Microsoft 365 environments with personal/team drive usage |
 SharePoint | Structured Microsoft document libraries and site-based sharing |
 Egnyte | File-server-heavy environments and IT-managed shared folders |
What changes after connection
Once a provider is connected and a project folder is chosen, the folder stops being just storage. It becomes a feed into the same file model used by direct uploads:
- files land in the project evidence list
- classification and extraction start automatically
- later upstream changes become new versions on the same evidence record
That means cloud sync is not a separate repository. It is just another way to populate the live diligence system.
What this does not replace
Cloud sync is about getting evidence into the project. It does not replace:
- External requests for follow-up asks
- Transcripts for call and meeting imports
- Webhooks for downstream automation
Use cloud sync when the document already exists somewhere. Use requests when the document does not exist in your evidence set yet and needs to be chased.