Branded Signatures for Every Mailbox
Design once, sync from your directory, and keep every person's signature correct across Google Workspace, Microsoft 365 and Zoho Workplace. Works withGmailOutlookZoho Mail
Hi Priya — thanks for the call. Short version: the new pricing holds for the whole term.
Best,
Amara Okafor
Head of Partnerships · Acme Group
amara@acme.example+44 20 7946 0521
Acme Group Ltd · 12 Ludgate Square · London EC4M 7AS
sendAs.Signs the mail your team already sends from
- Gmail
- Gmail mobile
- Outlook desktop
- Outlook on the web
- Outlook mobile
- Zoho Mail
A complete signature system for every part of the business.
Templates, brand kits, directory sync and drift checks in one place, written into each provider through the mechanism it actually supports.
Every mailbox, checked
Layerit reads each managed mailbox back and compares it with what you intended, so the dashboard matches what recipients actually see.
Mailboxes
acme.example · acme-labs.example
- GmailAmara Okaforamara@acme.exampleIn sync
- OutlookJonas Lindqvistjonas@acme.exampleIn sync
- GmailSupportsupport@acme.exampleIn sync
- OutlookPriya Ramanpriya@acme-labs.exampleDrifted
- GmailTomás Ferreiratomas@acme.exampleDevice signature
- Zoho MailLena Brandtlena@acme-labs.exampleIn sync
Directory record
- Name
- Amara Okafor
- Title
Partnerships Lead
Head of Partnerships- Phone
- +44 20 7946 0521
- Office
- London
Fields that survive a promotion
Names, titles and phone numbers are read from the directory that already owns them and re-read on a schedule.
- Acme Group · head officeAcme Group Ltd · logo, palette, footer
- Acme Labs · research unitAcme Labs GmbH · logo, palette, footer
- Acme France · Paris officeAcme France SAS · logo, palette, footer
A brand kit per unit, group or location
Logo, palette and legal footer belong to a business unit, a group or an office, so a company with three trading names gets three correct answers.
Built to work where your team already sends.
Three providers, three different signature mechanisms. Each one is used for what it genuinely does, and named where it falls short.
Google Workspace
users.settings.sendAs
The cleanest path of the three. Write HTML into sendAs and it reaches Gmail on the web — and, since April 2025, Gmail mobile falls back to it. No add-on required.
Native · web and mobileMicrosoft 365
Office.body.setSignatureAsync
Graph has no signature field at all. The add-in is the only mechanism that reaches Outlook desktop and mobile together, and it auto-runs only when an administrator deploys it.
Add-in · admin-deployedZoho Workplace
POST /accounts/{zuid}/signature
A per-user signature API with no organisation-level or bulk write. The signature it writes appears in Zoho Mail on the web and in the Zoho Mail mobile app.
Native · web and mobileNative write
Write into the provider's own setting and reach clients no add-in can.
Layerit renders the signature and writes it where the provider keeps it, through an admin API. No per-person consent, nothing for an employee to forget.
How the planes workPATCH sendAs/amara@acme.example
- Rendered from template
- Written to Gmail web
- Gmail mobile falls back to it
From
- amara@acme.example
- support@acme.example
- sales@acme.example
Signature: Acme Support team
Compose injection
Resolve the signature as the message is written for aliases and shared senders.
Where a compose hook exists, an add-in resolves the signature for the current From identity. When support@ writes, the signature says support@.
See shared sendersReconciliation
Know when a mailbox stops matching before a customer does.
Most providers let a person edit their own signature. Layerit reports the difference, which mailbox, and what it now says — drift is a fact to surface, not a surprise.
See drift reportingHi Priya — thanks for the call. Short version: the new pricing holds for the whole term.
Best,
Amara Okafor
Head of Partnerships · Acme Group
amara@acme.example+44 20 7946 0521
Acme Group Ltd · 12 Ludgate Square · London EC4M 7AS
No provider covers every client a person might send from. We read the vendor documentation before writing code, and we publish where the gaps are.
Coverage
What each integration actually reaches. Kept current as providers ship.
The qualifiers are part of the answer, so they are in the cells rather than in a footnote.
Known limitations| Client | Google Workspace | Microsoft 365 | Zoho Workplace |
|---|---|---|---|
| Webmail | Covered | Coveredadmin deploy | Covered |
| Desktop app | Covered | Coveredadmin deploy | Not covered |
| Mobile app | Coverednative fallback | Coveredadmin deploy | Not covered |
| Aliases and send-as | Conditionalper alias | Conditionalshared perm | Conditionalunverified |
| Shared mailbox | ConditionalGroups | Conditional1.13 required | Conditionalno signature object |
| Replies and forwards | Conditionalnew mail only | Covered | Conditionalscript dependent |
- CoveredCovered — by the provider's own API
- ConditionalConditional — the qualifier in the cell applies
- Not coveredNot covered
Google's sendAs signature is user-editable and reports drift. Microsoft's add-in covers replies and forwards because it writes into the draft. Zoho's signature is applied when composing on the web and in the mobile app.
Every signature correct. Every gap named.
Security
Small surface, on purpose. Nothing to secure that we never hold.
Layerit holds directory attributes and templates, and nothing else. Every write goes through the provider's own API.
Message bodies stored
0
Layerit writes through provider APIs and is never in the mail path.
Providers per plan
3
Google, Microsoft and Zoho on every tier.
Editable by employees
0
Every field comes from the directory or an administrator.
What we hold
- Directory attributes
- Templates and brand kits
- Reconciliation state
- Audit trail of changes
- Message bodies, subjects or attachmentsNever
Isolated by design
Separated at the database
Every organisation has a database of its own, so a query in one cannot reach another's rows.
Security detailQuestions
The questions we get asked first.
Does Layerit sit in our mail delivery path?
No. We write signatures through each provider's own settings and APIs. Mail is composed and delivered by Google, Microsoft or Zoho exactly as it would be without us. That means our worst failure is a stale signature, never a lost message — and we never hold message bodies, recipients or attachments.
Do employees have to install or learn anything?
On Google, no: the signature is written through the sendAs API and shows up in Gmail on the web and on mobile. On Microsoft, a user-facing add-in is the only cross-client path, and it works properly only when an administrator deploys it centrally — so that is what onboarding sets up. On Zoho, the native write needs nothing from the employee.
What happens when someone edits their own signature?
Layerit reads the mailbox back and reports the difference. Signature state is user-editable on most providers, so drift is a normal outcome rather than a bug: the product's job is to tell you it happened, which mailbox, and what it now says.
Does it work on phones?
On Google Workspace, yes — Gmail mobile falls back to the web signature when no device-local signature exists. On Microsoft 365, yes, through the add-in. On Zoho, yes — the signature written through Zoho's API shows in the Zoho Mail mobile app. One caveat we cannot fix in code: a device-local mobile signature always wins, and no API can detect or clear it.
What if we have more people than our plan allows?
On pay as you go there is no allowance to run past: everyone in the directory can be signed, and you pay for each signed user: each person whose signature Layerit has applied. On Enterprise, the console shows seats in use against the seats bought, so you can add more before a directory sync reaches the limit.
What data do you read?
Directory attributes needed to build a signature: display name, job title, primary address, phone numbers, office location and profile photo, plus the current signature value for reconciliation. No message content, ever.
Ready to sign every mailbox?