Google Workspace support

Last updated date:

Install, authorize, reconnect, and troubleshoot Google Workspace without sharing credentials or customer content.

1. Before you start

  • Choose the Seedling workspace that should own the organization-wide connection.
  • Confirm that you are a current administrator of that Seedling workspace.
  • For Marketplace installation, use a Google Workspace administrator and install Seedling for the entire organization.
  • Do not choose an organizational unit or group; partial installation is not supported in version 1.

2. Install from Google Workspace Marketplace

  1. Install Seedling for the entire Google Workspace organization.
  2. Open Seedling from the Google apps menu and sign in to Seedling.
  3. Select the Seedling workspace, review the data-use notice, and continue.
  4. Sign in to Google for identity verification. Seedling does not ask the user to reapprove the Workspace data scopes granted by the administrator installation.
  5. Wait while Seedling verifies the customer license, administrative access, and license coverage for every eligible active Directory user.
  6. Confirm that the connection becomes active and allow the initial Directory sync and per-user Gmail, Calendar, Drive, Sheets, and Meet synchronization to complete.

3. Connect a customer-managed service account

Never send the service-account JSON or private key by email or through an ordinary support ticket.

Reconnect existing installations after enabling Sheets and Meet and adding the Meet scope. Directory reconciliation upgrades administrator-only content sources to per-user coverage.

  1. Create a Google Cloud service account controlled by your organization.
  2. Enable the Admin SDK, Gmail, Calendar, Drive, Sheets, and Meet APIs, then configure domain-wide delegation for the exact seven read-only scopes in the integration guide.
  3. In Seedling, choose the customer-managed option and provide the administrator email, domain, and service-account JSON through the connection form.
  4. Connect and allow the initial Directory sync to create Gmail, Calendar, Drive, Sheets, and Meet sources for each eligible active user. Verify successful content sync; showing as connected alone does not prove Sheets or Meet API access.

4. Installation and authorization problems

Administrator required
Confirm both Seedling workspace-admin access and sufficient Google Workspace administrative access, then start again.
Partial organization coverage
Remove the partial OU or group assignment and reinstall Seedling for the entire organization. Seedling cannot activate while any eligible active user is outside the licensed population.
Organization already connected
One Google customer can map to only one Seedling workspace in an environment. Disconnect the existing workspace intentionally before replacement.
Missing scope or signing permission
Restore the exact read-only scope set or Seedling's configured keyless IAM signing permission. Seedling fails closed rather than storing a partial connection.
Temporary Google failure
Wait and retry. Temporary licensing, quota, or API failures do not delete existing customer data.

5. Contact Google Workspace integration support

Include the organization, Seedling workspace, installation mode, safe timestamps, and any non-sensitive result code. Never include passwords, OAuth tokens, service-account keys, email bodies, Drive files, or Calendar descriptions.

Email
support@tryseedling.ai
Initial response target
Within one business day. Security, privacy, and widespread service-impacting reports are prioritized; contracted terms control if different.