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.
Google Workspace email signature management with one signature manager for every org unit
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.
Sample company
Blocks
| Group | Mailboxes | Status |
|---|
What Workspace gives you on its own
The signature in each user's Gmail settings
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.
One template, filled per user, written to every send-as address
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.
- Groups follow your org unit structure, so a department or an office is a group without a new list.
- Aliases get the right template, which matters when one person answers from both a personal and a shared address.
- The short mobile variant covers the Gmail app on iOS and Android.
- Replies use the short block when you switch on reply-aware templates.
- Every rollout is a version, and rollback returns an org unit to the previous one in one click.
Connecting your tenant
What you approve, and what it covers
A Workspace administrator authorises the connection and confirms the org units in scope. The permissions cover reading directory profiles and setting Gmail signature settings for the users in scope.
- The authorisation lives in your own admin console, listed with your other connected applications, and you revoke it there.
- No mail is routed through AutoSignature, and message bodies are not read or stored.
- Nothing is installed on anyone's computer, and no extension is pushed to Chrome.
- Users keep the ability to write email exactly as they do today.
Running Workspace and Microsoft together
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.
Questions from Workspace admins
Can people still change their own signature?
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.
Does this work as a Google Workspace signature manager for aliases and shared addresses?
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.
What about signatures in the Gmail mobile app?
The Gmail app uses the signature on the account when it is configured to, and the short mobile variant is written for those few lines. That is what the mobile preview in the studio shows you before you deploy.
Do we need Google Cloud or a service account of our own?
No. You authorise the connection from the admin console and that is the whole setup on your side.