Google Workspace

Connect Google Calendar, Gmail, and Drive so the assistant and notetaker can use them.

The Google Workspace integration is what gets used during onboarding when you click Connect Google Calendar. It's a per-user OAuth connection that brings your calendar (and, where enabled, mail and drive) into MainBranch.

What gets connected

Calendar — Required for the meeting notetaker. The assistant can also reference upcoming and past events.
Gmail — Optional. When enabled, the assistant can search across your mail to answer questions.
Google Drive — Optional. When enabled, MainBranch indexes the documents you can access so they show up in search and chat.

Mail and drive are opt-in by your workspace admin from the Apps page.

Permissions requested

Only the minimum scopes for what's enabled are requested:

Basic profile info (name, email, openid).
Calendar read access if you connect your calendar.
Read access to mail and drive only if those integrations are enabled for your workspace.

MainBranch never asks for write access — it doesn't modify your Google data.

Connecting

Go to Profile settings → Integrations.
Click Google Calendar (or Google Workspace if mail and drive are enabled).
Sign in to your Google account on the consent screen.
Review the requested permissions and click Allow.
You'll be returned to MainBranch and your integration is active.

What changes after connecting

Upcoming meetings appear in the Meetings page.
The notetaker can join those meetings, subject to your meeting settings.
The assistant can search your calendar (and mail, drive, if enabled).
File source icons in the Vault and search show Google Drive for files synced from Drive.

Disconnecting

From the same Integrations page, click Disconnect next to Google. Your tokens are revoked and synced data is removed from MainBranch. Existing meeting recordings and transcripts are not deleted — only the live connection is removed.

Domain-wide installations

If your organization uses Google Workspace SSO, your admin may have configured a domain-wide install. In that case the consent screen is simpler and the admin's approval covers everyone. See Workspace → Authentication.