Skip to content

For IT teams

One connection. Then nothing to maintain.

Connect Google Workspace once with read-only directory access. Signifier writes the signatures, follows the directory, and hands the day-to-day to marketing. No script, no rerun, no tickets.

Connect with your Google admin account. No demo first.

What you grant

Two permissions, and you can read both

The connection reads the directory and writes one Gmail setting. It does not read mail, calendars, Drive or chat, and it never changes the directory. The consent screen and the security page say the same thing in the same words.

  • Directory, read onlyNames, titles, departments, phones, photos, org units, groups. Only the fields your templates use.
  • Gmail signature settingsThe one setting the product exists to manage. Not mail, not filters, not forwarding.
  • Revocable from your sideAdmin console → Security → API controls. One click, all access gone.

Rollout

Pilot group first, then everyone

Templates are assigned to the org units and Google Groups you already maintain. Assign one pilot group, publish, check a few inboxes, then assign the rest. Someone who moves teams gets the matching template on the next sync; nobody has to tell you.

  • Org units and groups you already haveNo parallel list of people. Signifier reads your structure and keeps up with it.
  • Joiners, movers, leavers: nothing to doA new account gets a signature on its first sync. A departure needs no cleanup.

After you hand it over

Marketing runs it. You can see everything.

Give marketing the editor role and they design templates and schedule banners without you. Connecting, locking and assigning stay with admins. The audit log records every change with who and when, so a question about the logo never becomes an investigation.

  • Admin, editor, viewerThree roles. The keys to the template without the keys to the connection.
  • Every change loggedWho edited, who published, who changed a date. Readable by admins at any time.

An afternoon's work

The rollout, step by step

  1. 1

    Connect with an admin account

    Grant the two permissions. The directory syncs within minutes.

  2. 2

    Marketing designs; you lock

    They build the template; you mark the brand parts and legal line as locked.

  3. 3

    Assign to a pilot group and publish

    Check a few Gmail accounts. Send one test to an outside address and open it in Outlook and on a phone.

  4. 4

    Assign the rest and step back

    From here, changes come from the directory or from marketing. Neither needs you.

Instead of a script

What you stop doing when you stop running GAM

Plenty of admins push signatures with GAM or the Gmail API and a CSV. It works, until the CSV is wrong. This is the difference, from the admin's chair.

With a script
A Cloud project, a service account and domain-wide delegation to set up and renew
A CSV to keep current by hand
A rerun every time someone joins, moves or is promoted
Marketing asks you for every banner, twice: to put it up and to take it down
Users edit the signature and it stays edited until the next run
With Signifier
One connection, granted once
The directory is the list
Changes follow the directory on their own
Marketing schedules banners; they start and stop by date
Locked parts are rewritten from the template on the next sync

FAQ

Questions IT asks first

Retire the signature script, keep the control

Two permissions you can read on the consent screen, templates assigned by the org units and groups you already keep, and marketing on the editor role. No GAM, no CSV, no rerun when someone is promoted.

Free for up to 5 people. Revoke access from the Admin console at any time.