Help

How to set up Gmail signatures for Google Workspace

Sigly pushes signatures directly into every user's Gmail across your Google Workspace domain — no add-ins, no browser extensions, nothing for employees to install.

This works through a Google service account with domain-wide delegation, using two narrow scopes: read-only directory access and Gmail signature settings. No email content is ever accessed.

Design your signatures

Create one or more signature templates in the builder and save them, ready to assign to people or departments.

Authorise Sigly in your Google Admin console

Go to Dashboard → Google Workspace. Sigly shows you a Client ID and two OAuth scopes. In your Google Admin console (admin.google.com) open Security → API controls → Domain-wide delegation, add the Client ID, and paste the scopes:

admin.directory.user.readonly — read your directory
gmail.settings.basic — set Gmail signatures

Connect your domain

Back in Sigly, enter your Workspace domain and a super-admin email, then click Connect.

Sync your directory

Click Sync directory to import your users along with their names, titles, departments, and phone numbers for personalisation.

Assign signatures

Set a default signature, then use per-person overrides or Bulk assign to apply a signature to an entire department in one click. Leave Personalise on so each user's own details are filled in automatically.

Deploy to Gmail

Click Deploy to Gmail. Sigly writes each person's personalised signature straight into their Gmail settings. Each user shows a status of Deployed, and any failures can be retried individually. When you update a signature later, just deploy again to push the change.

Where it works

There's no add-in here — Sigly sets the signature in the user's own Gmail settings, exactly as if they'd pasted it in themselves. That means it applies wherever Gmail's own compose window runs:

Where they read mail	Signature applies	Notes
Gmail on the web	Yes	—
Gmail app (iOS / Android)	Usually	Uses the account signature unless that person has set their own Mobile Signature in the app, which takes priority.
Apple Mail, Thunderbird, Outlook (via IMAP)	No	The signature lives in Gmail's compose window, not the mailbox, so other clients don't see it.
Aliases & send-as addresses	No	Only the primary send-as address is set. Other identities keep whatever signature they already had.

For anyone in the "No" rows, send them a self-install link — same personalised signature, pasted in once.

Prefer Microsoft? See Microsoft 365. No directory at all? Use CSV import.

Next: Create a professional email signature →

Open Google Workspace