Skip to main content

Google Workspace

Connection

Setup

1

Create a service account

In a Google Cloud project, create a service account and download the JSON key for it.
2

Delegate the scopes

Give the service account domain-wide delegation for the scopes under Permissions.
3

Choose the admin account

The service account acts on behalf of the specified admin. We recommend giving that admin only the privileges Klef actually needs.

Permissions

Delegate each scope, and give the admin the privilege beside it.
  • https://www.googleapis.com/auth/admin.directory.user, with user management and password reset, to manage users.
  • https://www.googleapis.com/auth/admin.directory.group, with groups, to manage group membership.
  • https://www.googleapis.com/auth/admin.directory.orgunit, with organizational units, to create org units and place users in them.
These are optional:
  • https://www.googleapis.com/auth/apps.licensing, with license management, to manage licenses.
  • https://www.googleapis.com/auth/admin.directory.rolemanagement, with managing admin roles, to manage admin roles.
  • https://www.googleapis.com/auth/admin.directory.user.security, with user security management, to revoke sessions when a user is suspended.
  • https://www.googleapis.com/auth/admin.datatransfer, with Data Transfer, to transfer Drive and Calendar data.

Settings

google_workspace.user

Fields

Credential: password

Password. A password { } block in a target issues it.

Default Account Matching Rules

When Klef adopts an account that already exists in Google Workspace, it works out whose it is by trying these in order. A connection can override them.

Examples

Google Workspace accounts

A suspended Google account before day one, licensed when they start, and suspended with its license returned when they leave.