How Sincerely works
Take email signatures off IT's plate: connect your Google Workspace, design once, and every mailbox stays on-brand automatically.
Setup
Live in an afternoon, not a quarter
Sign in with Google
Your Workspace domain becomes your organisation automatically, no verification emails, no DNS records. Colleagues who sign in with the same domain join on their own.
Connect your directory
One read-only connection to the Google Directory brings in every employee's name, title, phone, department and org unit. Nobody types a CSV. Synced nightly, human corrections always win.
Design once, assign by team
Build a template in the editor and lock the fields that carry your brand. Assign it to the whole company, an organisational unit, or a Google Group, Sales, Legal and Support each get the right one.
Everyone installs in one click
Each person gets a personal install link, no password, no training. The Chrome extension keeps every signature current from then on, re-syncing automatically every few hours.
Centralised control
Every signature from one dashboard
Push a rebrand, a new campaign banner, or updated legal text once, and every mailbox picks it up the same day. The deployment dashboard shows exactly who is current, who is stale, and who never installed, with one-click reminders.
Directory sync
Signature data that keeps itself current
Promotions, new phone numbers and renamed teams flow from your Google Directory into signatures automatically. New joiners are provisioned the day they appear; leavers are revoked the day they go, and their seat is freed.
Locked fields
Employees can't break the brand
Admins decide which fields each person may edit, typically their name, title and mobile. The logo, colours, layout, disclaimers and banner are locked on the server, not just greyed out in the interface.
Team targeting
The right signature for every team
Templates and campaign banners target the organisational units and Google Groups you already maintain, with subtree matching, assigning /Sales covers /Sales/EMEA. Priorities settle overlaps predictably.
Security
We never touch your email
No mail access, by architecture. Sincerely holds no Gmail scopes and doesn't sit in your mail flow, there is no credential in our system that could read or send a message.
Read-only directory, minimised. We store only signature-relevant fields, encrypt the Google connection at rest, and purge directory data the moment you disconnect.
Isolated by the database. Row-level security separates every organisation at the storage layer, data lives in London, and click analytics use hashed IPs, no pixels, ever.
What native Google Workspace leaves unsolved
The Admin console's append-footer is a disclaimer tool, not a signature manager. Full breakdown here.
| Capability | Native Workspace | Sincerely |
|---|---|---|
| Company-wide signature templates | No | Yes |
| Personalised per-employee details (merge fields) | No | Yes |
| Locked fields employees can't edit | No | Yes |
| Assignment by OU or Google Group | OU-level footer only | Yes |
| Auto-provision new joiners from the directory | Manual | Automatic |
| Sync titles and phone numbers from the directory | Manual | Automatic, nightly |
| Campaign banners with scheduling | No | Yes |
| Click analytics | No | Yes |
| Deployment visibility (who has installed) | No | Yes |
| Audit log of admin changes | No | Yes |
Questions, answered honestly
How do signatures actually get into Gmail?
Client-side, with nothing touching your mail flow. Each person's signature is written into Gmail's own signature setting, one click via our Chrome extension from their personal install link. The extension then re-checks every few hours and silently updates the signature whenever the template, the person's details, or the active campaign changes. Workspace admins on managed Chrome fleets can force-install the extension domain-wide from the Admin console, making rollout a single action.
What access does Sincerely need to my Google Workspace?
Sign-in uses only basic profile scopes. Directory sync adds three read-only Admin SDK scopes (users, groups, org units) authorised once by an admin. We hold no Gmail scopes at all, Sincerely cannot read, send or route a single email, and there is no server-side credential that could. Directory data is used solely to render the signatures you asked for, under Google's Limited Use policy.
Doesn't Google Workspace do this natively?
Not really. The Admin console's 'Append footer' is a compliance feature: rich text only, no per-person fields, OU-level granularity, appended below the quoted thread where nobody looks. It's the right tool for a legal disclaimer and the wrong one for signatures, many companies correctly use both.
What happens when someone leaves?
The nightly directory sync sees the suspension, revokes their install link, stops their extension syncing, and frees the seat. Nothing is hard-deleted, so a re-hired employee comes back cleanly. A safety guard prevents a directory hiccup from ever mass-suspending your roster.
Do employees need accounts or passwords?
No. Each member gets a personal install link by email, open it, one click, done. Signing in with Google is optional for members and takes one click when they want to edit their own details.
Will signatures look right in Outlook and Apple Mail?
Yes, that's most of the engineering. Your recipients read email in every client that exists, including classic Outlook for Windows, which renders HTML with Microsoft Word's engine. Every template is built and tested against that worst case: table-based layout, inlined styles, no webfonts, image rules that survive dark mode.
Stop the signature chaos
Standardised, on-brand signatures across your whole Workspace, set up before your next meeting starts.