Directory sync: email signatures that stay current with no re-typing

The number-one cause of wrong signatures is data: a title that changed, an outdated phone number, someone who moved teams. The fix isn’t to ask everyone to update their signature — it is to plug the signature into the source of truth: the company directory.

The principle

Your company already maintains a directory: its Google Workspace or Microsoft 365 accounts (Entra ID, formerly Azure AD). For each person it holds a name, an email address, and often a title, department, phone number and photo.

A signature management tool syncs that directory:

1. it pulls users and their attributes;
2. it turns groups into teams;
3. it pulls profile photos;
4. it re-runs the sync regularly, or on demand.

Each signature is then generated from a template and the person’s data.

Dynamic fields

In the template you don’t write “Julie Martin”, you write {{first_name}} {{last_name}}. When the signature compiles, each field is replaced with the directory value. The most common fields:

Field	Typical source
First and last name	User account
Job title	“Title” / “job title” attribute
Department / team	“Department” attribute or group
Office and mobile phone	Phone attributes
Office address	“Office” attribute or organization value
Photo	Account profile photo

Extra fields can live in the tool itself when the directory doesn’t hold them: booking link, personal LinkedIn profile, pronouns, and so on.

The key point: when the data changes in the directory (promotion, new number), the signature follows automatically, without anyone having to think about it.

From groups to teams

Directory groups (“Sales”, “Support”, “London”) become teams in the signature tool. That lets you:

• assign a different signature per team;
• target a banner at a team;
• automatically place a new hire in the right team as soon as they’re added to the right group.

See signatures by team and multi-brand.

Data quality: the real work

Syncing often reveals an uncomfortable truth: the directory is incomplete. Empty titles, inconsistent wording (“Sales Mgr”, “Sales manager”, “Head of Sales”), phone numbers in the wrong format.

Before rollout, plan a clean-up:

1. Export the attributes the signature uses.
2. Harmonize job titles (a reference list helps).
3. Normalize phone numbers (international format: +44 20 7946 0000).
4. Fill empty fields — or make sure the template hides empty lines.
5. Name an owner for the data (HR or IT) going forward.

This work benefits the whole company, well beyond signatures.

Handling edge cases

• Empty field: a good template hides the line automatically (no “Mobile:” followed by nothing).
• Service accounts and shared mailboxes: exclude them from the sync or give them a generic signature.
• Sensitive data: don’t publish a personal mobile number without consent. See email signatures and GDPR.
• Manual overrides: some tools let you correct a value for one person without touching the directory.

Sync history

A good tool keeps a history: what was created, updated, skipped — and why. It is invaluable for understanding why someone’s signature shows a given value, and for spotting directory anomalies.

In practice

• On Google Workspace, sync uses Google’s directory APIs with an administrator’s authorization. See the Gmail guide.
• On Microsoft 365, it goes through Microsoft Graph. See the Outlook guide.

Either way, an administrator steps in once. After that, joiners, leavers and role changes flow into signatures on their own — a topic we cover in signatures for joiners and leavers.