Connecting Google Workspace
Connect Gmail, Calendar, Drive, Docs and Sheets in one click — no OAuth client to register.
On SynapseOrch Cloud, Google Workspace is a platform connection: open the tools gallery, click Connect Google, approve the scopes Google shows you, and your agents can use Gmail, Calendar, Drive, Docs and Sheets.
There is no Google Cloud project to create and no OAuth client to register. That is the main practical difference from self-hosting, where the credential belongs to whoever runs the deployment, so you register your own.
What you are approving
Google shows you the scopes at consent time, and they are the ones the tools actually need — SynapseOrch does not ask for broader access than the tools it exposes.
The connection belongs to the person who authorised it. What agents can then do is bounded by that person's own Google permissions: connecting does not grant an agent access to anything you could not open yourself.
Revoking
Disconnect from the tools gallery, or revoke SynapseOrch from your Google account permissions. Either takes effect immediately; agents that were using those tools start failing that step rather than falling back to anything.
Using it
Once connected, the Google tools appear like any other tool — tick them on an agent, or call them from a Tool step.
Because these tools reach a system outside the workspace and can modify real data — sending mail, editing documents — they are a good first candidate for tool policy. Setting destructive to confirm puts you in the loop before an agent sends anything.
Per-user connections
A connection is currently shared at the organisation level rather than being per-member: agents act as the account that authorised it, not as whoever triggered the run. If you need an agent to act as each individual user, that is not available yet — connect a dedicated account rather than a personal one.