Updated: August 2026
Quick Answer. Zoho People syncs users in from Google Workspace and Office 365 but does not write employee data back, so a promotion recorded in Zoho People never updates a Google Workspace profile or an email signature. Zoho Mail's admin console can apply one organisation-wide signature that users cannot override, but it has no per-department templates, no banner campaigns, no click analytics, and it covers Zoho Mail only.
Related guides: which HR software syncs to Google Workspace, Keka email signatures, and centrally manage email signatures.
The short answer
Zoho People's directory integrations run inbound. It syncs users from Google Workspace and imports users from Office 365 to create Zoho People records. Nothing flows the other way. Its Google Workspace Marketplace listing asks only to see information about users on your domain, which is read access.
So a promotion recorded in Zoho People does not update anyone's Google Workspace profile, and therefore does not update anyone's email signature.
Centralize your team's email signatures in 7 days.
SyncSignature deploys signatures across Google Workspace and Microsoft 365 with directory sync. Teams plan from $2/user/mo (5-seat min). 7-day trial, no credit card.
The Zoho detail that explains the whole category
Zoho is the clearest illustration of a pattern that runs across every HR platform we checked, because Zoho owns both sides of it.
Zoho People, the HR product, reads from your directory. Zoho Directory, a separate product, writes to it: it provisions and deprovisions users in Google Workspace, creates accounts, and reflects changes to mapped profile fields into Google Workspace.
Even the vendor with an HRIS and an identity product under one roof keeps directory writing in the identity product. That is not a Zoho quirk. It is how the category is drawn. HR systems record what is true about people. Directories decide what accounts exist. Almost nobody bridges the two, and the ones who do sell to IT.
What Zoho Mail's built-in signature actually does
If you are on Zoho Mail as well as Zoho People, there is a genuine built-in option and it is worth knowing where it stops.
In the Zoho Mail Admin Console on paid plans, an admin can configure an organisation-wide signature template using placeholders that pull from user profile data, Zoho People fields, or custom fields. Usefully, a signature configured there cannot be overwritten by the signature a user sets themselves, which solves the single most common failure in signature management.
What it does not cover, per the same documentation: different templates targeted at different departments or groups, banner campaigns and scheduling, and click analytics. And it applies inside Zoho Mail only. If part of your company is on Gmail or Outlook, which is common after an acquisition or in a company that moved to Zoho gradually, those mailboxes are not covered at all.
For a single-brand company entirely on Zoho Mail that wants one template with no campaigns and no measurement, the built-in option is the right answer and you should use it. For anything past that, you are managing signatures somewhere else.
What to do if you are on Zoho People plus Google Workspace or Microsoft 365
This is the more common setup, and the built-in Zoho Mail option does not apply.
The practical route is to treat the directory as the source of truth for the six fields a signature actually uses: name, job title, department, work phone, office, and photo. Keep those current in Google Workspace or Microsoft 365, then let directory sync build and deploy signatures from them. Group targeting handles the rest, so a person moving from Sales to Product picks up the right template without anybody reassigning anything.
This does mean six fields get maintained in two places. That is the honest cost, and it is smaller than it sounds, because those six fields change when someone joins, changes role, or leaves, which is exactly when someone is already in both systems.
If your HR platform does expose employee data to read directly, that second place disappears. SyncSignature reads Google Workspace and Microsoft 365 directories, and reads Keka directly through its API.
Frequently asked questions
Does Zoho People sync employee data to Google Workspace?
No. Zoho People syncs users from Google Workspace into Zoho People, and imports users from Office 365. Its Google Workspace Marketplace listing requests read access to user information. It does not write job titles or departments back into Google Workspace profiles.
Can Zoho Mail apply one signature to the whole organisation?
Yes, on paid plans, through the Zoho Mail Admin Console, using placeholders that can pull from Zoho People fields. Users cannot override it. It does not do per-department templates, banner campaigns, or click analytics, and it covers Zoho Mail only.
What is the difference between Zoho People and Zoho Directory here?
Zoho People reads from your directory. Zoho Directory writes to it, including creating users in Google Workspace and reflecting mapped profile field changes.
We are half on Zoho Mail and half on Google Workspace. What now?
The Zoho Mail built-in signature covers only the Zoho Mail half. For one consistent signature across both, you need a tool that deploys to each platform. That is the normal reason companies in this position look at signature management software.
Centralize your team's email signatures in 7 days.
SyncSignature deploys signatures across Google Workspace and Microsoft 365 with directory sync. Teams plan from $2/user/mo (5-seat min). 7-day trial, no credit card.
Share this post