Google Drive
Google Drive as a storage target uses the same domain-wide delegation the Google Workspace connector sets up, impersonating one user to read and write their Drive.
What you need #
- A Google Workspace domain with Caryvane's service account authorised for domain-wide delegation (done once, on the Connectors page).
- The email of the Workspace user whose Drive this is.
- Optionally a root folder ID to scope the target to one folder.
Add it as a storage target #
- Connectors → Google Workspace → Connect and complete the delegation if it has not been done for this customer.
- Storage → Add → Google Drive, enter the user email (and folder ID).
- Test.
Test on the target's row proves the credentials; a target that fails shows the provider's own message until it is fixed. From then on it can be a job's destination, a cloud-to-cloud source, a cloud drive, or an archive.
What it supports #
| Capability | Google Drive |
|---|---|
| Streams uploads | No |
| Version history | Sidecar |
| Realtime cloud-copy source | No |
| Cloud-drive mount | Yes |
| Reachable from the Cloud Agent | Yes |
| Browse in the console | Yes |
Things to know #
Consumer Google accounts (gmail.com Drives) are deliberately not supported: Google requires a separate security assessment for that scope, and Caryvane is aimed at Workspace domains. The field is shown greyed so nobody wonders where it went.
Google-native documents (Docs, Sheets, Slides) are exported to Office formats when copied out; they have no bytes of their own.