> ## Documentation Index
> Fetch the complete documentation index at: https://university.triggr-app.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Workspace clients

> Run User Onboarding and User Offboarding in a client's Google Workspace instead of Microsoft 365.

Set a client's directory to Google Workspace and Core runs User Onboarding and User Offboarding in that client's Google Workspace, with the same approvals, tickets and credential delivery as Microsoft 365 clients.

## Set up a client

**1. Connect the client's Google Workspace**

Follow [Google Workspace](https://university.triggr-app.com/integrations/google-workspace.md) for the client, with an OAuth client or a service account with domain-wide delegation. Licences, Drive and Calendar transfer, mail forwarding and auto-reply need the service account.

**2. Set the directory**

On **Clients**, open the client and set **Directory** to Google Workspace. It can't change while one of the client's runs is in progress or waiting for approval, and a client synced with on-premises Active Directory keeps Microsoft 365.

**3. Choose the Google settings**

Open User Onboarding and User Offboarding, choose the client in the scope picker and set its Google settings, then click **Test for a client**.

## User Onboarding

| Setting | What happens |
| - | - |
| Groups | The new user is added to each group. |
| Licence | The new user gets the Google Workspace licence. |
| Org unit | The new user is created in it; without one, in the top-level org unit. |

The user is created on the client's primary domain with the form's name, job title, department and manager, and a temporary password they change at first sign-in. The welcome email points to Google sign-in.

## User Offboarding

Every offboarding resets the leaver's password and signs them out everywhere.

| Setting | What happens |
| - | - |
| Transfer Drive and Calendar | Moves the leaver's files and future events to their manager, or to a user chosen on the form. |
| Forward mail | Forwards new mail to a colleague in the same domain. |
| Auto-reply | Turns on an auto-reply, optionally between two dates. |
| Remove from groups | Removes the leaver from every group. |
| Leaver org unit | Moves the account to it. |
| Delete | Deletes the account once the transfer has finished, and removes the licences Core assigned. |

Google bounces mail sent to a suspended account, so when forwarding or an auto-reply is on, the account stays active but locked. Otherwise Core suspends it, or deletes it if Delete is on. If a transfer is still running after 30 minutes, the account is suspended instead of deleted and the ticket says so.

## Readiness

Test for a client and Home check each Google Workspace client:

| Problem | Fix |
| - | - |
| Google Workspace isn't connected for this client | Click **Connect Google Workspace**, then Authorize on the client's row. |
| Can't read the client's Google Workspace | Authorize again as a super admin, or check the service account's domain-wide delegation scopes. |
| Google settings need a service account | Add a service account with domain-wide delegation, or turn off licences, transfer, forwarding and auto-reply. |
| Service account can't change Gmail settings | Add the Gmail scopes to the service account's domain-wide delegation. |

The assistant can switch a client's directory (you approve it) and walk you through each of these.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.