How to sync your Google Workspace directory to iOS and Android
Three approaches, in 2026: manual per-employee, MDM contact distribution, and automated directory sync. Which one fits your team — with the tradeoffs each one actually hits in practice.
If your company runs on Google Workspace and you want your team to have their colleagues’ contacts on their phones — names, numbers, photos, all of it, always current — there are exactly three real approaches in 2026. Each works in different sized teams. Each has tradeoffs that aren’t obvious until you’ve tried them.
This guide walks through all three, in order from simplest to most automated, and helps you decide which fits your team.
The three approaches at a glance
| Approach | Set-up effort | Maintenance effort | Best for |
|---|---|---|---|
| Manual per-employee | None | High (every employee, forever) | Teams under 10, staying small |
| MDM contact distribution | High (per-device enrollment) | Medium (centralized but separate list) | Teams 200+, with existing MDM |
| Automated directory sync | Low (one admin setup) | Near-zero (auto from directory) | Teams 10–500, growing |
The rest of this post breaks down each one — what you actually do, what fails, and what it costs.
Approach 1 — Manual per-employee
There is no setup. Each employee just adds colleagues to their own contacts as they meet them.
Pros:
- Zero admin work.
- Works on any phone, any OS, no enrollment required.
- No subscription cost.
Cons:
- New employees never get a fully populated list.
- People who change roles, leave, or update their phone numbers create dead entries on every other employee’s phone.
- After 12 months, every contact list reflects a fossilized snapshot of who that person happened to email in the past.
- Photos stay stale or never get added.
- Caller ID coverage is patchy at best — colleagues you talk to often, fine; the rest of the org, unknown numbers.
When this works: teams of fewer than ten people, where everyone is in the same room and the entire roster fits in someone’s head.
When it stops working: the moment you add a 6th person, hire your first remote worker, or have someone change roles.
Approach 2 — MDM contact distribution
MDM stands for Mobile Device Management. Tools like Microsoft Intune, Jamf, Hexnode, or Google Workspace’s own endpoint management can push contact lists to enrolled devices.
How it works
- Employees enroll their phones in your MDM, granting the company control over certain device settings.
- An admin maintains a contact list — either inside the MDM UI or imported from a CSV.
- The MDM pushes that list to enrolled devices as managed contacts.
- Changes to the list propagate to all enrolled devices on the next sync.
Where it actually fails
The conceptual problem: the contact list lives inside the MDM, not inside Google Workspace. Your directory is still the source of truth for everything else (Gmail autocomplete, Calendar invitations, etc.) — but the contact list is now a separate maintained artifact. They drift. Within months, the MDM list is months behind the directory.
The practical problem: MDM enrollment is a big ask, especially for personal phones. Many employees push back on the company managing their device, even with limited scope. Smaller teams find that asking for MDM enrollment for what is essentially a contact list problem is disproportionate.
The cost problem: MDM platforms charge per device per month, typically €4–10. For a 50-person team, that’s €200–500/month — to solve a contact sync problem that is one feature out of fifty MDM features.
When this works: companies that already run MDM for other reasons (security policy enforcement, app distribution, device wipe on loss). Contact distribution is then a low-effort addition.
When this is wrong: SMB or mid-market companies that don’t currently have MDM and would deploy it primarily to sync contacts. The infrastructure is overbuilt for the problem.
Approach 3 — Automated directory sync
A purpose-built sync tool reads your Workspace directory on a schedule and delivers it as a contact feed to each employee’s phone via a mobile app.
How it works
- An admin sets up a Google Cloud service account, enables domain-wide delegation with a read-only directory scope, and pastes the credentials into the sync product.
- The product reads the directory every hour (or on manual trigger).
- Each employee installs a small mobile app, signs in with their Google work account, and the directory becomes available on their phone — name, phone, email, title, department, photo.
- As the directory updates, employees’ phones reflect the change automatically on the next sync.
Why it works
- Single source of truth: the directory in Google Workspace stays authoritative. No second list to maintain.
- No device management: the sync runs through an app, not at the device-management level. Personal phones don’t get enrolled in anything corporate.
- No per-employee admin work: once the directory is connected, every employee in the workspace gets access automatically. New hires appear on phones within hours of being added to Workspace.
- Per-field control: good sync products let an admin choose which directory fields are exposed. Hide salary, internal extensions, or HR-only data without restructuring the directory itself.
Tradeoffs
- Mobile app required: employees need to install something. For most teams this is a low ask. For some it’s an extra step.
- Subscription cost: any good automated tool charges per user per month. Plan for €1–3 per user per month in this market segment.
- Initial setup: the Google Cloud service account + domain-wide delegation step takes about 15 minutes the first time. Once done, it doesn’t need ongoing attention.
Which one to choose
Run through these questions in order:
- Is your team under 5 people, expected to stay that way, and everyone already knows each other? → Manual is fine. You don’t really have a contact sync problem.
- Do you already run MDM for other reasons? → Add contact distribution to your existing MDM. The marginal effort is low.
- Neither of the above? → Use an automated directory sync tool. This is what they’re built for, and what you’ll spend least time on.
For most companies in the 10–500 employee range, option 3 is the right answer. It’s the only one that scales without ongoing manual work and doesn’t require infrastructure designed for a bigger problem.
A note on bidirectional sync
A question that comes up: can the mobile app also write changes back into the directory? Update a colleague’s phone number, edit a title, add new colleagues?
Workspace Sync is read-only by design. That’s a deliberate choice — bidirectional sync introduces edit conflicts, permission complexity, and the risk of accidentally mangling the authoritative directory. The directory should be maintained by an admin in Workspace, where the existing approval workflows and audit logs already work. The mobile app’s job is to surface that directory, not to be a second editing interface for it.
For most use cases, this is what you actually want.
Setting up Workspace Sync (option 3)
If you decide on option 3 and pick Workspace Sync specifically, setup is one read-only connection: a Google Cloud service account with domain-wide delegation, scoped only to admin.directory.user.readonly — read-only, directory-only, no other access. A Google Workspace super admin creates it, authorises it in the Admin console and uploads its key to the Workspace Sync dashboard, which runs the first sync straight away. Then you give app access to the people who need it, and each one signs in to the mobile app with their work Google account.
End-to-end: about 15 minutes for the admin, near-zero for employees.
Every screen of it, step by step, is in the Help guide: Connect Google Workspace.
Closing
If you’re at the “do nothing” stage — team under 5 — you can sit with manual for a while. If you’re at the “this is starting to hurt” stage and over 5 people, automated sync is genuinely the only approach that doesn’t require ongoing admin effort.
See pricing — free for up to 5 users; from the 6th user, every user is €1 per month (+ VAT). No credit card to start.