Product

How Sig.Surf works with Google Workspace

An admin says yes once and Sig.Surf handles the rest. There is nothing to install on anyone's computer.

The three steps

  1. Design a signature

    Use the studio with a template, the AI designer or an imported signature. Add fields such as name and title, and Sig.Surf fills them in per person.

  2. Authorize once

    A Google Workspace super admin adds Sig.Surf under Domain-wide delegation in the Google Admin console, granting two scopes: one to write the Gmail signature and one to read users from the directory.

  3. Deploy

    Sig.Surf reads your directory, picks the right signature for each person, renders it and writes it to their Gmail settings. Unchanged signatures are skipped, and if a grant fails or is revoked, Sig.Surf tells you.

Who gets which signature

Assign a template to everyone, a department, a group or a person, or to everyone whose directory details match conditions you set, such as a job title that contains “Sales”. When several assignments match, the highest priority wins, then person over conditions over group over department over everyone, then a usage-specific assignment over a general one, then the newest.

What this covers

  • Gmail on the web, iOS and Android, for new messages, because the signature lives in the account's Gmail settings.
  • A different signature for replies and forwards is not covered. Gmail's API holds one signature per address and applies it to new messages only. That needs the Chrome extension, which works in Gmail on the web in Chrome.
  • No mail is routed through Sig.Surf, and Sig.Surf cannot read your messages.

What you control

  • Revoke Sig.Surf's access at any time in the Admin console.
  • Lock the fields employees must not change. On the Growth plan employees can edit the fields you allow from the employee hub.
  • Use Sig.Surf without an admin: copy a signature into Gmail on the web by hand.

Step by step: Deploy signatures to a Google Workspace domain.

This page is also available as Markdown.