> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/configuration/google-workspace-integration.md).

# Google Workspace Integration

Connecting Google Workspace to Augmentt pulls your GWS employees into the platform so you can map users to devices in Discover and manage GWS users through User Management in Engage.

{% hint style="danger" %}
**Google Workspace integration does not support the Secure module**, and Secure-related reports will show no data for GWS-only tenants. Secure's posture monitoring, MFA tracking, and Conditional Access management are Microsoft-only capabilities today.
{% endhint %}

## What Engage supports for Google Workspace

Engage supports a **subset** of user-management actions for GWS — specifically, anything that doesn't depend on Microsoft-only objects. Actions relying on Exchange mailboxes, Entra Temporary Access Passes, or the Global Address List aren't available for Google Workspace accounts, since those objects don't exist in GWS.

{% hint style="warning" %}
If you're coming from an M365-only workflow, don't assume feature parity. Confirm a specific Engage action (password reset, offboarding, account creation, etc.) is supported for GWS before relying on it for a client — the exact support matrix is maintained separately and may change as GWS support expands.
{% endhint %}

## Setup steps

1. In the Augmentt portal, go to **Configuration > Integrations**.
2. Select the customer account you wish to connect.
3. Click **Sign In with Google** in the Google Workspace integration box.
4. Enter your Google Workspace admin credentials.
5. Check the boxes to grant Augmentt the necessary permissions, then click **Continue**.
6. Confirm the connection succeeded — the Integrations page should show **Connected** in the Google Workspace box for that customer.

## Known limitations

| Area                       | Limitation                                                                                                                                                                        |
| -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Secure module              | Not supported for GWS; no posture data                                                                                                                                            |
| Reports                    | No data populated for GWS-only tenants                                                                                                                                            |
| Scheduled user offboarding | Not currently available for GWS users the way it is for M365 (M365 supports scheduling; GWS offboarding is a manual/immediate action)                                             |
| Discover device mapping    | Requires the user to have a corresponding account Augmentt can map to — mapping GWS users to devices has had reported gaps for GWS-primary tenants (see below)                    |
| New account creation       | License-selection during test-account creation for GWS has had reported issues in some environments; if the license dropdown appears empty and you can't proceed, contact support |

## Common issues

**"Can I use Secure/MFA management with Google Workspace?"** No — Secure and its MFA/Conditional Access management features are Microsoft-only. GWS integration is for Discover (SaaS usage/device mapping) and the supported subset of Engage user management.

**Discover can't map users to devices for a GWS-primary client.** This has been reported for clients that are primarily Google Workspace — if device-to-user mapping only seems to work for M365 accounts and you can't select a GWS account, contact support with the tenant name; this is a known gap area rather than a configuration mistake on your end.

**Domain not showing when creating a new user.** If the domain selector is empty or won't populate when trying to create a test/new user account for a GWS-integrated tenant, don't assume the integration itself is broken — this has been reported as an isolated UI issue and should be reported to support with the tenant name.

**"Nothing seems to sync after connecting."** If licenses, groups, or newly created accounts aren't reflecting after a sync, try disconnecting and reconnecting the integration first. If the problem persists after a fresh connection — especially missing groups or a large percentage of users showing incorrect license data — escalate to support with the tenant domain and specific examples (which users/groups are missing) rather than continuing to reconnect repeatedly.

{% hint style="info" %}
Google Workspace support in Engage has expanded over time (for example, password reset actions now work for GWS in current releases). If you're unsure whether a specific action is currently supported, check with support rather than assuming based on older documentation or community posts.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.augmentt.com/configuration/google-workspace-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
