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

# Gmail

> Connect Gmail to centralize and act on email threads with your partners.

## Overview

The Gmail connector monitors a Gmail inbox for quoting activity between you and your partners. Unlike the [Outlook](/connectors/outlook) integration, which requires manual Azure AD configuration, Gmail uses a simplified OAuth flow.

***

## Setup

1. In the Seminode app, go to **[Settings → Connectors <Icon icon="arrow-up-right" />](https://app.seminode.com/settings/connectors)**
2. In the Gmail section, click **Add**
3. Enter the **Email Address** you want to monitor (e.g., `quotes@company.com`)
4. Click **Authorize with Google**
5. Complete the Google consent screen to grant Seminode access
   * If Google shows an app-verification notice, ask your Google Workspace administrator to pre-approve the Seminode OAuth app in the Admin Console (Security → API controls → App access control) — the consent screen then proceeds without a notice.
6. On successful authorization, you'll be redirected back and the configuration is saved automatically

<Tip>
  Before your first connection is set up, the Gmail section shows a copyable email template you can send to your IT team requesting account creation.
</Tip>

<Warning>
  Use a shared inbox email, not a personal one — emails from connected accounts are visible to all team members with inbox access.
</Warning>

<Note>
  Connector management is permission-gated. If you don't see an **Add** button, ask an administrator to grant you connector access.
</Note>

***

## IT Security: Why a Dedicated Google Workspace Account Is Required

This section provides technical context for IT teams evaluating the account requirements for this integration.

### Why Google Groups Cannot Be Used

Google Groups are distribution lists — they forward incoming emails to group members but do not function as standalone Google accounts. As a result:

* Google Groups have no account identity and **cannot authenticate via OAuth 2.0**
* It is not possible to sign into a Google Group or generate OAuth tokens on its behalf
* The Gmail API, which Seminode uses to read, parse, and manage emails, requires a **real authenticated Google account** to authorize access
* There is no workaround — this is a fundamental limitation of how Google Groups are architected

### Why OAuth 2.0 Is Required

Seminode's integration reads, parses, and processes inbound quote emails programmatically. To do this securely and reliably, the application must access the Gmail API using OAuth 2.0 — the only authentication method Google supports for this type of integration.

OAuth 2.0 provides the following security properties:

* Seminode can only access the specific inbox it has been explicitly authorized to access
* The account password is never stored anywhere in Seminode's systems
* Access can be revoked at any time by your IT team without changing the account password
* Authorization is logged and auditable in the Google Workspace Admin Console

### Why a Dedicated Account Is Preferable to a Shared One

A dedicated account assigned solely to this integration provides meaningful security and operational benefits:

| Benefit            | Detail                                                                             |
| ------------------ | ---------------------------------------------------------------------------------- |
| Clear audit trail  | All activity on the account is attributable to the Seminode integration            |
| Revocation control | IT can revoke access at any time without impacting other users                     |
| Security isolation | The account has a limited, defined purpose with no access to other systems         |
| Stability          | No risk of unrelated password changes or policy changes disrupting the integration |

### Required Account Configuration

When requesting account creation from IT, the account should be configured as follows:

* **Account type**: Google Workspace user account (not a Google Group or distribution list)
* **Purpose**: Dedicated inbox for receiving partner quote emails processed by Seminode
* **OAuth scope granted**: The following Gmail API scopes are requested during authorization:

| Scope            | Classification | Purpose                                |
| ---------------- | -------------- | -------------------------------------- |
| `gmail.modify`   | Sensitive      | Read, archive, label, and trash emails |
| `gmail.readonly` | Sensitive      | Read-only access to inbox              |
| `gmail.send`     | Sensitive      | Send on behalf of the account          |

* **Credentials**: Standard Account credentials — Google handles authentication, Seminode never stores the password or account information
* **Access control**: IT retains full administrative control and can revoke the OAuth grant at any time via the Google Workspace Admin Console

<Note>
  Seminode's OAuth access is limited to the inbox you authorize. It does not access other Google services, other accounts, or any data outside the designated mailbox.
</Note>

***

## Managing Configurations

Each connected Gmail account appears as a row showing the monitored email address and a connection status indicator:

* **Green** — connection active
* **Red** — connection failed
* **Gray** — connector disabled or status unknown

Available actions:

* **Toggle On/Off** — enable or disable monitoring without removing the configuration
* **Test** — verify the connection is working
* **Reconnect** — shown when the connection test fails; re-runs the Google authorization to restore a failed connection
* **Delete** — permanently remove the configuration

<Warning>
  Deleting a Gmail configuration cannot be undone. You'll need to re-authorize through Google to reconnect.
</Warning>