Google Workspace integration

The Google Workspace integration connects Bigmind to your company’s Google Workspace domain so we can sync calendar events and email conversations across your team (without asking every user to connect individually).

Company-wide vs personal (and why it matters)

Bigmind supports two ways to connect communication data. Which one you’re using determines whether you should set up Google Workspace or connect tools user-by-user:

  • Company-wide mode (recommended for teams): An admin installs Bigmind in Google Workspace once, and Bigmind can sync calendar/email for domain users (subject to your Workspace admin settings and which users are licensed/enabled). In this mode, setup happens in Settings → Communication data → Google Workspace.
  • User-by-user mode: Each team member connects their own calendar and email account (for example, Google Calendar + Gmail). Owners can see progress across the team, but each user authorizes their own connection.
  • Personal workspace (solo): If you’re using Bigmind as an individual (not inside an organization tenant), you connect your calendar/email directly from the Integrations screen.

If you’re not seeing the Google Workspace option, your organization may be in User-by-user mode. Organization owners can switch modes from the setup flow (“Change setup mode”).

What you get with Google Workspace

  • Calendar sync: Import calendar events so Bigmind can connect meetings to the right people, accounts, and deals.
  • Email sync: Import email threads so Bigmind can understand the full customer conversation (before and after meetings).
  • Better attribution: With calendar + email context, Bigmind can attribute activity to the right CRM records more reliably.
  • Send email from Bigmind (optional): Use the “Send email” tool to draft emails with AI, then the user manually reviews and clicks Send.
  • Meeting recordings (optional): If recordings are enabled for a meeting and your team wants to view them inside Bigmind, Bigmind can retrieve and display recordings from Google.
  • Google Drive files (optional): Connect Drive so proposals, contracts, and other documents can be pulled into context and associated to the right CRM records.

Data security and where you’ll see this in Bigmind

  • Encrypted storage: Imported email content and calendar event data are stored in an encrypted way.
  • Visible in the app: When you have a CRM connected, Bigmind can associate imported emails and calendar events to CRM records (Contacts, Leads, Accounts, Deals). Those associations are visible inside the Bigmind app in the relevant activity/context views.

To learn exactly how matching works (and what you can configure), see Activity attribution.

Setup overview

  1. Verify your organization domain in Bigmind (required). The integration is configured per domain.
  2. Install the Bigmind app from Google Workspace Marketplace for your domain. In Google Admin, you can optionally limit access to specific Organization Units (OUs)—only users in enabled OUs will be able to use Bigmind’s Google features.
  3. Connect in Bigmind at Settings → Communication data → Google Workspace.
  4. Choose what to import (Calendar events, Emails). Imports only run when the connection is healthy.

Limiting the integration to an Organization Unit (OU)

When you install Bigmind from Google Workspace Marketplace, Google Admin lets you enable the app for:

  • Everyone in the domain, or
  • Only specific Organization Units (OUs) (recommended when rolling out gradually).

If you limit Bigmind to a specific OU, users outside that OU will appear as not enabled (even though the domain install is active). Bigmind will only sync and allow access for users in enabled OUs.

Why we request each OAuth scope

Bigmind uses a domain-wide Google Workspace connection. This means your admin authorizes Bigmind at the domain level so we can sync the data you explicitly enable (calendar and/or email) for users in your Workspace.

https://www.googleapis.com/auth/admin.directory.user.readonly

  • What it enables: Listing users in your Google Workspace domain (via the Admin Directory API).
  • What Bigmind uses it for: Showing the Users table, determining which users are eligible for sync, and running per-user calendar/email sync safely and consistently.
  • Customer value: One domain connection can cover the whole team (and you can monitor who is syncable) instead of relying on every individual user to connect.

https://www.googleapis.com/auth/calendar

  • What it enables: Reading calendar events and setting up calendar change notifications (webhooks/watch channels) for near real-time updates.
  • What Bigmind uses it for: Importing meetings, keeping meeting data fresh, and associating meetings to the right people and CRM records.
  • Customer value: Better meeting coverage (including reschedules/updates) and more accurate activity attribution—without manual logging.
  • Note: Bigmind does not create or edit your calendar events as part of this integration.

https://www.googleapis.com/auth/gmail.readonly

  • What it enables: Reading Gmail message metadata and content needed for syncing email threads.
  • What Bigmind uses it for: Importing email conversations so your team’s deal context includes “what happened over email” in addition to meetings.
  • Customer value: A more complete view of customer engagement, better follow-ups, and higher-quality AI outputs because Bigmind sees the whole conversation.

https://www.googleapis.com/auth/gmail.compose and https://www.googleapis.com/auth/gmail.send

  • What it enables: Creating a draft and sending email via the user’s Gmail account.
  • What Bigmind uses it for: The Send email tool. Bigmind can generate a suggested email, but the user is always prompted to review and explicitly confirm before sending.
  • Customer value: Faster, higher-quality follow-ups with human-in-the-loop control.
  • Important: Emails are never sent in an automated way by default. Automated sending is only enabled if a customer explicitly requests it via their account manager.

https://www.googleapis.com/auth/meetings.space.readonly

  • What it enables: Reading Google Meet conference/recording metadata.
  • What Bigmind uses it for: Discovering and listing recordings only when a meeting has recording enabled and the user chooses to view the recording inside Bigmind’s meeting page.
  • Customer value: One place to review the meeting (transcript, insights, and recording) without hunting for links.

https://www.googleapis.com/auth/drive.readonly and https://www.googleapis.com/auth/drive.file

  • What it enables: Accessing files stored in Google Drive.
  • What Bigmind uses it for: Retrieving Google Meet recordings (recordings are stored in Drive) and enabling Drive documents (proposals, contracts, etc.) to be pulled into context and associated to the correct CRM records.
  • Customer value: Better deal context and easier collaboration by connecting relevant documents to the right accounts/deals.
  • Privacy model: These scopes are used for user-initiated actions (for example, loading a recording in a meeting page, or attaching a relevant Drive file). Bigmind does not “crawl” your Drive indiscriminately.

https://www.googleapis.com/auth/appsmarketplace.license

  • What it enables: Checking whether the Bigmind Marketplace app is installed and enabled for your domain/users.
  • What Bigmind uses it for: Connection health checks (so the UI can tell you whether Marketplace installation is complete and whether specific users are enabled by admin policy/OU).
  • Customer value: Faster, clearer setup and troubleshooting—so admins can confirm installation status without guesswork.

https://www.googleapis.com/auth/userinfo.email

  • What it enables: Verifying the admin identity used during connection checks.
  • What Bigmind uses it for: Testing that OAuth/domain delegation is working correctly.
  • Customer value: More reliable connection diagnostics and fewer “it looks connected, but sync isn’t running” situations.

Troubleshooting tips

  • Status is “Disconnected”: Confirm Marketplace installation and that your organization has a verified domain in Bigmind.
  • Status is “Partially connected”: Marketplace is installed, but OAuth/domain access isn’t healthy yet. Reconnect and confirm domain-wide permissions in Google Admin.
  • Status is “Ready”: Connection is healthy, but imports are not enabled. Turn on Calendar and/or Email imports.
  • Status is “Active”: Imports are enabled and sync should be running.
  • Some users can’t access Bigmind Google features: Check whether the Marketplace app is enabled only for specific OUs. Users outside enabled OUs will show as not enabled.