Email signature generator › Google Workspace
Setting signatures for everyone in Google Workspace
Google Workspace can enforce a footer on every message an organisation sends, without touching anyone's settings. It is a blunt instrument, and understanding where it is blunt saves a rollout.
Your details
Layout
Logo or photo — optional
Drop an image here or click to choose
PNG or JPG, under 2 MB
or use a hosted image
Preview
Nothing is uploaded and nothing is stored. The image you drop stays in this browser.
Where the setting is
- Admin console → Apps → Google Workspace → Gmail → Compliance.
- Find Append footer and configure it.
- Scope it to an organisational unit or a group if it should not apply to everyone.
The footer accepts HTML, and supports a small set of placeholders that pull from each user's directory profile — name, title, department, phone — so one template can produce a personalised block for every employee.
Limit one: it is appended on the server
The footer is added as the message leaves, not while it is being written. That means the sender never sees it in their sent copy in the way the recipient sees it, and it lands at the very bottom of the message — below any personal signature the user has set, and below the quoted thread on replies.
On a long thread the compliance footer therefore ends up buried under all the quoted history. If the point of the footer is legal disclosure, that is usually still acceptable. If the point is branding, it is not.
Limit two: internal mail
There is a setting for whether the footer is appended to internal messages as well as external ones. Leaving it on for internal mail means every one-line message between colleagues carries the full block, which people find irritating quickly. Most organisations scope it to outbound only.
Limit three: placeholders are only as good as the directory
If the template uses the job title placeholder and half the directory has no job title filled in, half your organisation sends a signature with a blank line where the title should be. Audit the directory fields before rolling out a template that depends on them, and design the template so a missing field collapses cleanly rather than leaving a stray comma.
When to use the personal signature instead
For branding and contact details, a signature set per user in Gmail settings sits above the quoted text, appears in the compose window, and can be edited by the person whose name is on it. For legal disclosure that must be on every message regardless of what the user does, the admin footer is the right tool. Many organisations use both, and should keep them from duplicating each other.
Rolling it out without a week of complaints
An organisation-wide footer appears on everyone's mail at once, including mail already in flight, and the first thing that happens is that people notice the parts that are wrong. Two steps avoid most of that.
Scope the rule to a single organisational unit containing two or three volunteers first, and leave it there for a few days. They will send real mail to real recipients and find the problems that a test message does not: how it looks under a long thread, what happens on a reply from the phone, whether the directory field for their team is populated.
Then check the directory before widening the scope. A template that uses the job title placeholder needs job titles; a template that uses the phone placeholder needs phone numbers in a consistent format. A directory audit takes an hour and prevents a footer that reads "Anna Meier, , Acme" for a third of the company.
Keeping it from duplicating the personal signature
If people already have their own signatures with name, role and phone, and the admin footer adds the same three things, every message carries them twice. The usual resolution is to divide the responsibilities: personal signatures carry the person, the admin footer carries the company and whatever is legally required. Say that explicitly when you announce the change, because otherwise half the organisation will delete their own signature and half will not.
What the footer cannot do
It cannot appear in the compose window, so people cannot see it as they write. It cannot be placed above the quoted text. It cannot be omitted for one message when the sender judges it unnecessary. Those are consequences of adding it on the server, and they are the price of it being unavoidable.
Frequently asked questions
Can I force a signature that users cannot remove?
Yes, with the Append footer setting under Gmail compliance. It is added server-side, so users cannot edit or remove it.
Why does the appended footer land under the quoted thread?
Because it is appended to the whole message as it is sent, not inserted at the cursor. There is no setting to place it higher.
Can the footer be personalised per user?
Yes, using directory placeholders for name, title, department and phone — provided those fields are populated.
Does the footer apply to messages sent from the mobile app?
Yes. Because it is applied on the server it covers every client, which is one of its main advantages.