Google Workspace footer vs signature: what to use
Google Workspace's Append footer setting adds the same block of text to every outgoing message from the users you choose. It cannot insert each person's own name, title or phone number. So it is right for a legal notice or a company line, and wrong for a personal signature. For individual signatures, an admin has to write each user's Gmail signature through the Gmail API, by script or with a tool.
The question "can Google Workspace automatically append a footer with the user's name?" shows up regularly in Google Workspace communities. The short answer is no, not with the footer alone.
What the footer does
In the Admin console, go to Apps > Google Workspace > Gmail > Compliance > Append footer. You can add text or basic HTML and apply it to an organisational unit or group. Google adds it when the message leaves, so:
- Everyone in scope gets the identical footer.
- The sender does not see it while composing.
- It is added to each outgoing message, so long threads can show it several times.
- It can be applied to messages to external recipients only, if you choose.
What it cannot do
- No per-user fields. There is no placeholder for the sender's name or title.
- No per-alias variation. Every address in scope gets the same text.
- Limited design control. It is fine for a few lines of text, but not meant for a designed signature with a photo.
How to give each person their own signature
Gmail stores each user's signature on their "send as" address. An admin with domain-wide delegation can set it with the Gmail API, and tools such as GAM wrap that in a command. The steps:
- Create a service account with domain-wide delegation for the Gmail settings scope.
- Build an HTML template with placeholders.
- For each user, fill in their details and call the API to set the signature on their primary address and any aliases.
- Rerun when details or the template change.
That is reliable, but someone has to own the template HTML and the script.
Use both
Many organisations use both: a personal signature for identity, and a short server footer for the legal notice that must never be removed. If you do, keep the footer short so it does not dominate replies.
Where Sendoff fits
Sendoff does the second part for you. Connect Google Workspace on the Team plan, and Sendoff reads your directory, builds each person's signature from your template and writes it to Gmail through the Gmail API, aliases included. When you change the template, you push the update to everyone. Steps are on the Google Workspace integration page. For the plain admin method, see our Google Workspace company signature guide.
Sendoff writes the web signature. It does not add a server footer and does not write the Gmail mobile app's separate signature field.
FAQ
Does the footer appear in the Gmail app? It is added on Google's servers, so it is added to mail sent from any device.
Can users remove the footer? No. That is why it suits mandatory notices.
Sources
- Google Workspace Admin Help, "Add a standard footer to outgoing emails": https://knowledge.workspace.google.com/admin/gmail/advanced/add-a-standard-footer-to-outgoing-emails
- Google Workspace Admin Help, "Set up Google Workspace user signatures in Gmail": https://support.google.com/a/answer/176652
- Google for Developers, "Manage aliases and signatures with the Gmail API": https://developers.google.com/workspace/gmail/api/guides/alias_and_signature_settings
Make yours now
Every Sendoff template is built to the rules in these guides. Free, no account needed.