The append footer in the admin console
Workspace can append a footer to outbound mail for the domain. It is a single block of text for everyone, it lands at the bottom of the thread rather than under the message, and it carries no per-person data.
In Google Workspace the signature belongs to the send-as address, which is why the admin console can set a footer for the domain but cannot give each person a correct, on-brand signature. AutoSignature sets the real signature, per user and per alias, from one template.
| Group | Mailboxes | Status |
|---|
The short answer
Google Workspace email signature management means one admin sets every Gmail signature in the company from a single template, instead of each person editing their own settings. The admin console can only append a fixed footer, the same text for everyone in an org unit, to outgoing mail. A signature manager uses the Gmail API to write a personal signature to each user and send-as alias, filled from the directory and grouped by org unit.
AutoSignature does this for Google Workspace and Microsoft 365 on every plan, from $49 a month per company on yearly billing for up to 25 mailboxes and $149 for up to 150. Gmail only tools such as SignatureSatori cost less per user; the comparison table below has the numbers.
Workspace can append a footer to outbound mail for the domain. It is a single block of text for everyone, it lands at the bottom of the thread rather than under the message, and it carries no per-person data.
This is the real signature: it sits under the message the sender writes, it can hold a logo and a layout, and it can differ per send-as address. On its own, it is also the one that each person sets themselves, differently.
Some well-known signature tools never reach this setting: CodeTwo, for example, is Microsoft 365 only. The tools that do cover Gmail are priced side by side in CodeTwo Google Workspace alternatives.
AutoSignature reads the profile fields in your directory and writes the rendered signature into each person's Gmail signature, for the primary address and for the send-as aliases you choose.
Your administrator creates a service account and JSON key in your Google Cloud project with Admin SDK API and Gmail API enabled, adds its Client ID under Domain-wide delegation in the Google Admin console with the directory and Gmail settings scopes, and pastes the key and an admin address into AutoSignature. The four ways to get one company wide email signature in Gmail, with their yearly cost, are compared on a separate page.
If part of the company is on Microsoft, connect that tenant too and share the template set between them. The Microsoft side is described on the Office 365 email signature management page.
List prices read on each vendor's own pricing page in September 2026, annual billing. Two well known tools are missing from the Gmail column entirely, which catches out companies that run both platforms.
| Tool | Google Workspace | List price | How it reaches Gmail |
|---|---|---|---|
| AutoSignature | Yes, every plan, same depth as Microsoft 365 | $99, $299 or $799 a month flat, half that yearly | Written to each user's Gmail signature |
| Exclaimer | Yes, separate Google Workspace product | $0.90 to $1.75 per user a month, 10 user minimum | Gmail signatures set from Google Directory |
| SyncSignature | Yes | $2 per user a month, $1.60 from 30 and $1.44 from 70 seats; quote above 100 | Written to Gmail directly |
| BulkSignature | Yes | $0.88 per user a month, 10 seat minimum | Google Directory sync and Gmail deployment |
| WiseStamp | Yes | $19 to $189 a month plus $1 per employee | Server side only on Platform and Enterprise |
| Newoldstamp | Yes | $1.33 to $1.83 per signature a month; quote above 200 | Google Workspace integration |
| Letsignit | Yes, native Gmail | $2 per user a month, annual only | Native Gmail integration |
| SignatureSatori | Yes, Gmail only | $1.11 per user a month at 5 users down to $0.50 at 1,000 | Gmail API with a daily directory sync |
| Email Signature Rescue | Yes, installed per user | $99 to $499 a year up to 20, then $2 per user a month | Signature Key and browser extension on each device |
| Bybrand | Yes, plus Microsoft 365 by Outlook add-in | $8 a month plus $0.50 per synced employee, monthly | Google Workspace APIs, aliases and multiple domains |
| CodeTwo | No, Microsoft 365 only | $0.91 to $1.22 per user a month | Not available |
| Sigsync | No, Office 365 and Exchange only | About $0.60 to $0.72 per user a month yearly | Not available |
Most per user tools are cheaper than us at 25 to 100 people, and the table says so. Where a flat price pays off is near the top of a band, around 120 to 150 mailboxes against the mid priced tools, and anywhere Gmail and Outlook have to carry the same signature from one account. The step by step admin setup is in the guide to managing Gmail signatures in Google Workspace.
Technically Gmail lets them, and the next rollout puts the managed signature back. Companies that want the change to stick immediately deploy to that org unit again, which takes seconds.
Yes. Each send-as address you include takes a template of its own, so a person answering from the support address signs as support rather than as themselves.
The Gmail app has its own mobile signature setting, which we do not write to. The short mobile variant is written for those few lines, ready to copy into the app. That is what the mobile preview in the studio shows you before you deploy.
Yes. Your administrator creates a service account and JSON key in your Google Cloud project with Admin SDK API and Gmail API enabled, adds its Client ID under Domain-wide delegation in the Google Admin console with the directory and Gmail settings scopes, and pastes the key and an admin address into AutoSignature.
Connect a signature manager to your Google Workspace admin account, build one template with placeholders for name, title and phone, and deploy it by org unit. The tool reads each person's details from Google Directory and writes the finished signature to their Gmail settings. Google's own Append footer setting only adds identical text below every message.
Not a personal one from the Admin console alone. An admin can add a compliance footer under Apps, Google Workspace, Gmail, Compliance, but that footer is the same for everyone and appears below the reply chain. Setting each user's own Gmail signature needs the Gmail API, which is what signature management tools use.
Connect AutoSignature using your own service account and domain-wide delegation, design a single template, choose the org units it applies to and deploy. Every user gets the same layout filled with their own details, including send-as aliases. When something changes, you edit the template once and deploy again.
Exclaimer, WiseStamp, BulkSignature, Newoldstamp, SyncSignature, Letsignit and AutoSignature all support Google Workspace. CodeTwo Email Signatures 365 and Sigsync do not; they cover Microsoft 365 only. If you run Gmail and Outlook side by side, check that both platforms are included in the plan you are pricing.
Per user tools run from about $0.88 to $2 per user a month on annual billing, usually with a 5 or 10 user minimum. AutoSignature is a flat $99 a month for up to 25 mailboxes, $299 up to 150 and $799 up to 600, or half that on a yearly plan, with Google Workspace included on every plan.