Google Workspace
Google Workspace support is in final verification
Votra's Google Workspace integration is built and in provider verification. Connecting is disabled until Google completes its review — this page explains exactly what that means, with no vague promises.
In final provider verification. Connecting is disabled until Google completes its review — no customer data is touched before then.
What the integration covers when it ships
- Discovery across Google Drive, Shared Drives and the Admin Directory.
- The same ownership-transfer and approval workflow already live on Microsoft 365.
- Delegated administrator consent — Votra acts through a Workspace admin account you designate.
- Requested scopes are minimal and read-biased: drive.metadata.readonly, admin.directory.user.readonly, drive.file.
What you can do today
Microsoft 365 offboarding and ownership transfer is fully live, and the pricing covers it: every plan includes both providers — when Google ships, existing organizations get it without a plan change. If your offboarding program is Google-centric today, the fastest path is to talk to sales about the verification timeline and pilot priority.
Why verification takes time
Google reviews apps that request Workspace admin scopes before granting broad access. The review gates what the app can do against tenants Votra has never seen — which is exactly the protection you want before the platform touches your directory. Votra deliberately does not accept Google connections until that review clears, because a provider promise is a promise to customers.
What Votra is
Votra builds TransferOps, a platform for running employee offboarding and resource-ownership transfers on Microsoft 365 — with Google Workspace following once its provider verification completes. Operations discover what an employee owns, move ownership and access through provider APIs without ever moving file content, enforce approval before anything changes, and export a signed audit trail of every action.