> For the complete documentation index, see [llms.txt](https://docs.teleskope.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teleskope.ai/connectors/saas/google-chat.md).

# Google Chat

{% hint style="info" %}
**Beta connector.** Google Chat support is being rolled out to early customers. The enrollment steps and scopes below are accurate; your Teleskope contact confirms the final scope list with you during onboarding.
{% endhint %}

Teleskope classifies Google Chat **messages** and **shared files** for sensitive content across 150+ entity types, the same engine used for Google Drive and Slack. Findings appear in the Data Catalog, drive Policy Maker rules, and support remediation actions on violating messages.

Google Chat uses the same Google Workspace domain-wide delegation as the [Google Drive](/connectors/saas/google-drive.md) connector. If you already enrolled Google Drive, you extend the existing service account rather than creating a new one.

## Prerequisites

* A Google Workspace administrator who can manage Domain-Wide Delegation.
* The unique Teleskope service account ID (shared by Teleskope, or already in use for Google Drive).
* Your Teleskope user has the **Admin** role.

## Setup Domain Wide Delegation

1. In [Google Workspace Admin](https://admin.google.com), go to Security > Access and Data Control > API Controls > Domain Wide Delegation (manage domain wide delegation).
2. Add the Teleskope service account ID, or edit the existing Teleskope entry if Google Drive is already enrolled.
3. Under Scopes, ensure the following are present (comma-separated). These let Teleskope discover spaces, read message and file content, resolve members, and act on violating messages:

| Scope                                                        | Purpose                                  |
| ------------------------------------------------------------ | ---------------------------------------- |
| `https://www.googleapis.com/auth/chat.spaces.readonly`       | Discover spaces                          |
| `https://www.googleapis.com/auth/chat.messages.readonly`     | Read message content                     |
| `https://www.googleapis.com/auth/chat.memberships.readonly`  | Resolve space membership                 |
| `https://www.googleapis.com/auth/chat.admin.spaces.readonly` | Enumerate spaces across the organization |
| `https://www.googleapis.com/auth/chat.admin.memberships`     | Grant the Teleskope app access to spaces |
| `https://www.googleapis.com/auth/chat.messages`              | Delete violating messages (Policy Maker) |

{% hint style="info" %}
Classification requires the read scopes plus `chat.admin.spaces.readonly` and `chat.admin.memberships`, so Teleskope can discover and join spaces. The `chat.messages` scope is required only if you enable Policy Maker remediation actions.
{% endhint %}

The directory scopes used to resolve users and groups (`admin.directory.user.readonly`, `admin.directory.group.readonly`) are shared with Google Drive. If Drive is already enrolled, they are already present.

## Create Teleskope Super Admin User

Google Chat administrative operations are performed as a licensed Super Admin user that Teleskope impersonates. If you enrolled Google Drive, reuse that user.

1. In Google Workspace Admin, go to Directory > Users > Add new user and create a user for the Teleskope service account (e.g. `teleskope@company.com`).
2. Ensure the user is licensed (cloud identity is sufficient).
3. Go to Account > Admin roles and assign the user the Super Admin role.
4. Share the email of the Super Admin user with Teleskope.

## Enroll in Teleskope

1. Navigate to Settings > Connectors > Google Chat.
2. Click **Enroll+**.
3. Confirm the Workspace domain and service account shown.
4. Click **Enroll**.

Teleskope discovers spaces across the organization, grants its app access, and begins scanning messages and shared files. Real-time monitoring of new and edited messages begins once enrollment completes.

## Remediation

Policy Maker rules can act on Google Chat findings, including deleting violating messages and notifying data owners. The remediation actions available for your workspace are confirmed during onboarding.

## Classifications & Filtering Behavior

Teleskope handles certain elements in specific ways. Below is a summary of the filtering logic and the elements not detected, for storage and noise-reduction reasons.

### Credit Card Numbers

Credit card numbers must pass post-validation, meaning they pass [Luhn Algorithm](https://en.wikipedia.org/wiki/Luhn_algorithm) checks.

### Social Security Numbers

While certain SSNs such as `123-45-6789` are **structurally valid** under SSA assignment rules, Teleskope proactively **filters out common test patterns or sequences** that are far more likely to be false positives. This reduces noise and inaccurate detections during scanning.

### Email Addresses

Teleskope **filters out internal and company-specific email addresses** during scans, to reduce noise and manage storage, particularly during historical scanning where repeated internal contacts are storage-intensive.

{% hint style="info" %}
The following elements are **also skipped for similar storage and filtering reasons**:

* `WEBSITE`
* `FIRST_NAME`
* `LAST_NAME`
* `MIDDLE_NAME`
* `USER_IDENTIFIER`
* `LANGUAGE`
* `ORGANIZATION`
  {% 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:

```
GET https://docs.teleskope.ai/connectors/saas/google-chat.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.