> ## Documentation Index
> Fetch the complete documentation index at: https://docs.blinq.me/llms.txt
> Use this file to discover all available pages before exploring further.
# Google Workspace email signature sync
> Push Blinq email signatures straight into your team's Gmail accounts, and keep them updated when they change.
Email signature sync is available on **Business** and **Enterprise** plans. [View pricing →](https://blinq.me/pricing)
Blinq writes your team's email signatures directly into their Gmail accounts. An admin creates a signature in Blinq, and it appears in Gmail without anyone having to copy or paste anything.
Sync is one way. Signatures move from Blinq into Gmail, and changes made in Gmail don't come back to Blinq.
**Looking for single sign-on?** That's a separate integration with its own setup — see [SAML SSO with Google Workspace](/identity/sso/google-workspace), filed under Integrations. The two are independent, and you can use either without the other.
## Prerequisites
* You must be an **Admin** or **Owner** in your Blinq workspace, on a Business or Enterprise plan.
* You'll need **Google Workspace Super Admin** access, or someone who has it and can complete their part of the setup.
* Your domain must be verified in Google Workspace. A Workspace subscription alone isn't enough.
* Each person's Blinq signature email must match a Gmail account in your Google Workspace.
## What sync does and doesn't do
| Behavior | Detail |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| Direction | One way, Blinq to Gmail |
| Which Gmail field | The default signature for **new emails** only. The reply and forward signature isn't set. |
| Changes made in Gmail | Overwritten the next time Blinq syncs that signature |
| Signatures per person | One. Google allows a single signature per address, so someone assigned two templates can only receive one. |
| Google Workspace tenants | One per Blinq workspace. Organisations running more than one tenant can't cover them all. |
| Signature and card | Not linked. Editing someone's card later doesn't change a signature already created from it — edit the signature itself. |
| Mobile | Image signatures don't render in the Gmail mobile app. |
**Install the Blinq app for your whole organisation, not for selected groups.** Scoping the Google Marketplace install to specific groups or organisational units is the most common reason signatures fail to sync, and the error it produces reads only **Sync failed** — nothing points at the scope. If you must limit it, make sure every person who'll receive a Blinq signature is inside the groups you select.
## Signatures aren't created for you
Adding someone to your workspace doesn't generate a signature for them. An admin creates each signature in Blinq first, and the sync then matches it to a Gmail account by email address. See [Creating a team email signature](https://support.blinq.me/en/articles/76202-creating-a-team-email-signature) for that step.
**HTML signatures are switched on by request.** By default a Blinq signature is a single image linking to the person's card. If you want an HTML signature instead, email [support@blinq.me](mailto:support@blinq.me) to have it enabled for your workspace.
## Documentation for Google Workspace signature sync
Authorise Blinq, choose your domains, and install the app from Google Marketplace.
Turn on the sync, push existing signatures, and read the sync statuses.
Signatures that won't sync, misleading error text, and signatures that don't appear in Gmail.
### Need help?
For any questions or issues, [contact Blinq support](https://support.blinq.me/en/) or email [support@blinq.me](mailto:support@blinq.me).