# Deploy signatures to Gmail for a Google Workspace domain

Source: https://sig.surf/docs/google-workspace-deployment (Markdown version of the page)

A Google Workspace super admin authorizes Sig.Surf once. After that Sig.Surf writes each person's signature to their Gmail settings, with no software on anyone's computer.

> Admin deployment is on the Team and Growth plans.

## Steps

1. Sign in to Sig.Surf with your Google Workspace account. Sig.Surf creates a workspace and an organization for you.
2. Create or pick a template, and choose who gets it: everyone, a department or a group.
3. As a **super admin**, open the Google Admin console and go to **Security**, then **API controls**, then **Domain-wide delegation**. Add Sig.Surf's client ID (Sig.Surf shows it during setup) with the two scopes listed below.
4. Run a deployment. Sig.Surf writes each person's signature to their Gmail settings. Signatures that have not changed since the last deployment are skipped.

## Scopes you grant

| Scope | What Sig.Surf uses it for |
| --- | --- |
| `https://www.googleapis.com/auth/gmail.settings.basic` | Write each user's send-as signature. Sig.Surf uses no other Gmail endpoint. |
| `https://www.googleapis.com/auth/admin.directory.user.readonly` | Read users from your directory so names, titles and phone numbers fill in. Read-only. |

## What it covers

- Gmail on the web, iOS and Android, for new messages. See the [iOS](https://sig.surf/docs/gmail-ios) and [Android](https://sig.surf/docs/gmail-android) notes.
- **Not covered:** different signatures for replies and forwards. Gmail's API holds one signature per address and uses it for new messages only, so those rules need the [Chrome extension](https://sig.surf/docs/chrome-extension).
- Mail is never routed through Sig.Surf.

## Revoking access

Remove Sig.Surf's entry under Domain-wide delegation in the Admin console. Sig.Surf can no longer write to any mailbox in your domain. Signatures already saved in Gmail stay as they are until someone changes them.
