# Gmail deployment for Google Workspace

Source: https://sig.surf/integrations/gmail-deployment (Markdown version of the page)

Sig.Surf writes the right signature into each person's Gmail settings. Nothing is installed on anyone's computer, and mail never passes through Sig.Surf.

- [Step-by-step guide](https://sig.surf/docs/google-workspace-deployment)

## How it works

1. A super admin authorizes Sig.Surf once in the Admin console under domain-wide delegation, with the Gmail signature scope and the directory read-only scope.
2. For each person, Sig.Surf picks the winning assignment, renders the signature with their details and writes it to their send-as settings.
3. Signatures that have not changed since the last run are skipped. A revoked or missing grant is reported instead of ignored.

## What it covers

- Gmail on the web, [iPhone and iPad](https://sig.surf/docs/gmail-ios) and [Android](https://sig.surf/docs/gmail-android), for new messages, because the signature lives in the account's Gmail settings.
- It does **not** set a different signature for replies and forwards. Gmail stores one signature per address and uses it for new messages only. Those rules need the [Chrome extension](https://sig.surf/integrations/chrome-extension).

## What it does not do

- It does not read, send or delete mail. Sig.Surf asks for no scope that allows it.
- Sig.Surf is not listed on the Google Workspace Marketplace yet, and Google's security review of apps that use restricted Gmail scopes is not complete. See [security](https://sig.surf/security) for current status.
