Connect & Integrate Google Workspace

Last updated: May 6, 2026

Introduction

This guide covers using YeshID's Google Workspace integration to connect your Google Workspace tenant.

Once connected, YeshID imports:

  • Users

  • Groups

  • Group memberships

  • Google Workspace admin roles

YeshID can also manage:

  • User create, update, activate, deactivate, and delete

  • Group membership changes

  • Admin role assignments

Steps

  1. Sign in to YeshID as an admin Open the Google Workspace integration setup in YeshID.

  2. Start the Google Workspace connection flow YeshID uses its managed Google OAuth application for this integration, so you do not need to create your own Google Cloud OAuth app.

  3. Sign in with a Google Workspace admin account Use a Google Workspace admin account for the consent flow. For the smoothest initial setup, use a Super Admin account.

  4. Review and approve the requested Google Workspace scopes YeshID requests these Google Admin SDK scopes:

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

    • https://www.googleapis.com/auth/admin.directory.group

    • https://www.googleapis.com/auth/admin.directory.group.member

    • https://www.googleapis.com/auth/admin.directory.rolemanagement

  5. Complete the OAuth consent flow Once consent is granted, YeshID stores the connection and can use it for sync and provisioning actions.

  6. Save the integration If YeshID shows any remaining configuration fields, save the integration once the OAuth connection is complete.

  7. Run a sync Start a sync in YeshID.

YeshID will import Google Workspace users, groups, group memberships, and admin role assignments that are accessible to the connected admin.

FAQ

Do I need to create my own Google OAuth app?

No.

This integration currently uses the YeshID-managed Google OAuth application.

What does YeshID import from Google Workspace?

YeshID imports:

  • Users

  • Groups

  • Group memberships

  • Google Workspace admin roles assigned to users

What can YeshID manage after setup?

YeshID can manage:

  • User lifecycle actions such as create, update, activate, deactivate, and delete

  • Group membership changes

  • Google Workspace admin role assignments

Why are admin roles missing or failing to sync?

Usually this means one of these is true:

  • The connection was authorized before the role-management scope was added

  • The OAuth grant was not reauthorized after a scope change

  • The connected admin account does not have enough Google Workspace admin privileges

If needed, reconnect and reauthorize the integration.

Why are group or user actions failing even though OAuth succeeded?

OAuth success only means Google accepted the consent flow.

Provisioning actions can still fail if the connected admin account does not have enough Google Workspace administrative privileges for the target operation.

Do I need a Super Admin forever?

Not necessarily.

A Super Admin is the safest choice for initial setup and troubleshooting. If your organization uses a narrower delegated admin model, you can test whether a lower-privilege admin role is sufficient for the specific YeshID actions you want to use.