Updated: August 2026
Quick Answer. Deel, Rippling and HiBob all provision accounts and push attribute updates into Google Workspace and Microsoft Entra ID. None of them sets email signatures, because a signature is not a directory attribute. It is HTML written into each person's mail client settings. Closing the gap needs a tool that reads the directory and writes signatures into each mailbox, server-side into Gmail settings and through an Outlook add-in for Microsoft 365.
Related guides: which HR software syncs to Google Workspace, automate signatures from employee data, and server-side vs client-side signatures.
The short answer
Provisioning and signatures are different problems, and solving the first does not touch the second.
Deel creates Google Workspace accounts and its field mapping explicitly covers job title and department, one way, with a daily sync. Rippling creates accounts, buys and assigns licences, and pushes attribute updates on a cadence you set. HiBob creates users, keeps attributes current, and deactivates them at offboarding. All of that works.
And the signature still says Account Executive, because a signature is not a directory attribute. It is a block of HTML sitting in each person's mail client settings, and nothing in your HR stack has ever written to it.
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.
Why the last step is missing everywhere
Directory attributes are structured fields with an owner. A signature is a rendered artifact: layout, logo, disclaimer, social icons, and a banner, assembled from those fields and then written into a per-user setting in Gmail or Outlook.
HR platforms do not build that, because it is not HR software. Identity platforms do not build it, because the write target is a mail client setting rather than a directory object. So the chain runs HR to directory and stops, one step short of the only place your customers ever see the data.
The irony is that companies with the best provisioning have the worst version of this problem. Their directory is genuinely accurate, which makes the gap between directory and signature purely a plumbing failure, not a data failure. The data is right there. Nothing is reading it.
What actually closes it
Something has to read the directory and write signatures into each mailbox. That is the whole job.
For Google Workspace, that means reading the Admin SDK Directory API and writing the rendered signature to each user's Gmail settings through the sendAs API. It is a server-side write, so it applies on desktop, mobile, and webmail without anybody installing anything.
For Microsoft 365 it takes two pieces, because Microsoft has no server-side API for writing Outlook signatures. Read-only Microsoft Graph access supplies the employee data, and an Outlook add-in deployed through Centralized Deployment renders the signature. Both are required. Graph alone cannot deploy, and the add-in alone has no data.
SyncSignature directory sync does exactly this on both platforms, on read-only directory permissions, and never routes or reads your email.
The three things that break next
Once signatures are wired to the directory, the failures move upstream and get smaller. Worth knowing in advance.
Inconsistent titles. Your HR platform will happily sync Sr. Software Engineer for one person and Senior Software Engineer for another. The directory is now accurate and your signatures are now visibly inconsistent. Fix it in the HR platform, since that is where the string is authored.
Empty fields. Manager, mobile number, and profile photo are the three that are usually blank, and a blank field is worse in a signature than in a directory because it renders as a gap or a stray label. Fallback values and hiding a row when its field is empty are what keep a half-populated org looking intentional.
Sync direction on offboarding. Confirm which way your HRIS runs. Deel, for example, pushes from Deel to Google Workspace on HRIS and EOR setups, and pulls the other way on its IT product. If the direction is not what you assumed, leavers linger.
Frequently asked questions
If Rippling already provisions accounts, why do I need anything else?
Provisioning creates and updates the account and its directory attributes. It does not write a signature into Gmail or Outlook. Those are separate write targets, and no HR or identity platform in this comparison writes signatures.
Can Deel or HiBob set email signatures directly?
No. Neither of them, and no other HR platform we checked, has a native email signature feature. They keep the directory current, which is the input a signature tool needs.
Do I need to change my HR setup to fix signatures?
No, and that is the good news. If your provisioning already works, the directory already has what a signature needs. You are adding one read-only consumer of data you are already maintaining.
What if my HR platform does not provision at all?
Then you have a bigger version of the same problem, and the options are different. See which HR software syncs employee data to Google Workspace for what each platform does and does not do.
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