When you sync your Google Workspace directory to every employee’s phone, an obvious question comes up: should everyone see everything?
Workspace directories accumulate fields over time. The HR team added “Hire date” three years ago. Finance added “Cost center.” Operations added “Internal extension.” Each was added for a legitimate reason inside the admin console. None of it was meant to land in a junior designer’s phone contact card next to “Marko Petrović — Senior Engineer.”
The thing the directory exposes isn’t always the thing the team should see. Workspace Sync is built around that distinction. This post explains how the per-field controls work, why they exist, and which fields most companies should think twice about exposing.
The default and the override
When we sync your Workspace directory, we don’t pass every field through to the mobile app. The default surface is intentionally minimal:
- Full name
- Phone numbers
- Job title
- Department
- Photo
Beyond that, every additional field is opt-in per company. In the admin dashboard, under Fields, you’ll see a list of every directory field that exists in your Workspace, each with a toggle. On means “send this to the mobile app.” Off means “don’t.”
The change takes effect immediately. Toggle a field off at 2pm; by 2:01pm, the next API call from any phone in your company excludes that field. There’s no caching layer where stale settings persist.
What companies typically hide
A few patterns show up across most setups.
Internal extension numbers
Many companies maintain VoIP extensions as a directory field — extension: 4281 or similar. These are useful inside the office, on the desk phones, where they were intended. They aren’t useful on mobile, and dialling a four-digit number from outside the office goes nowhere helpful.
Worse: extensions occasionally leak in ways that weren’t planned. An employee sends a colleague’s contact card to a client. The client now has the internal extension number. Not catastrophic, but the kind of small leak that adds up.
Most companies hide this field on mobile. Office extension stays in the directory for desk-phone use; mobile employees see the regular phone number only.
Manager hierarchy
Workspace tracks who reports to whom. This shows up in Gmail (when someone replies-all on an internal thread, the org chart is visible implicitly) and is useful for routing approvals.
But every team member’s phone showing “Reports to: Marko Mršić” is a different thing. It surfaces hierarchy in a way that not every culture wants to make explicit. Some companies expose it — they’re proud of the org structure and want it visible. Others find it makes peer-to-peer interactions feel more hierarchical than they want.
There’s no right answer. The toggle exists so each company decides.
Cost center and finance fields
Larger Workspaces often store department cost codes, finance attribution, location codes, and other operational metadata in the directory. These power reports and integrations on the admin side, but they’re meaningless to an individual employee picking up a colleague’s contact card.
These fields almost always stay hidden. There’s no upside to exposing them and a slight downside if an employee finds them confusing or, worse, treats them as something to discuss publicly.
Custom HR fields
Some companies use Workspace custom fields for things like:
- Birthday or hire anniversary (for celebration automation)
- Employee ID number
- Office building or floor
- Personal phone (in case business phone is unavailable)
Each has a legitimate use elsewhere, and each is a privacy decision when exposed on a phone. Personal phone numbers in particular: employees who provided them for HR records didn’t necessarily consent to every colleague having them in their phone contacts.
What companies typically keep visible
The defaults — name, work email, work phone, title, department, photo — are visible for a reason. They’re the minimal set that makes the directory useful at all:
- Without the name, there’s no contact.
- Without the phone, you can’t call.
- Without the email, you can’t send a message outside of internal tools.
- Without the title and department, employees in larger teams have no quick way to know who’s responsible for what.
- Without the photo, new employees can’t put faces to names.
A few companies turn off the photo for cultural reasons (some industries treat employee photos as personal information that shouldn’t be widely distributed). The other defaults stay on in essentially every setup.
The principle: directory ≠ destination
The mental shift that makes per-field configuration feel natural is this:
The directory is a database. The mobile contact list is a surface. They don’t have to contain the same set of fields.
You don’t expose every column of your CRM to every salesperson’s phone. You wouldn’t expose every Slack profile field to every channel. Directories are no different — they contain rich metadata, and rich metadata is useful in admin contexts and confusing or invasive in employee-facing contexts.
The default of “show everything because it’s there” is a mistake people make once, get pushback on from someone whose information was exposed in a way they didn’t expect, and then never make again. Setting per-field defaults from the start avoids the pushback entirely.
GDPR and data minimization
A practical note for European customers: under GDPR, the principle of data minimization says you should only expose the personal data needed for a specific purpose. A directory sync that exposes “every field because we can” arguably exceeds the lawful basis on which employees provided their data.
Configuring per-field controls — exposing only what’s necessary for the directory’s purpose (calling, emailing, knowing what role a colleague has) — keeps you well inside the minimization principle and gives you a concrete audit answer if it ever comes up.
We don’t intend this to be legal advice. But the alignment between practical defensibility and good defaults is worth noting: doing the privacy-aware thing also happens to be the legally cleanest thing.
Adjusting after the fact
What happens if you sync first, then realise you exposed a field you shouldn’t have?
Two steps:
- Toggle the field off in the admin dashboard. Immediate effect — within seconds, no mobile app fetches the field again.
- Existing data on devices clears on the next sync. Mobile apps don’t retain fields the API stops returning. Within minutes, every employee’s phone reflects the new field set.
There’s no “this got exposed and now it’s permanently out there” risk. Toggle off, and it’s gone from devices on the next refresh.
Closing
Per-field control isn’t a flashy feature, and it doesn’t usually make landing-page copy. It’s also one of the most-used features in real customer accounts, especially after the first few weeks when companies look at what they’re syncing and realise they want to dial it back.
If you’re evaluating directory sync tools, the question worth asking is: which fields does this product send to the mobile app by default, and how do I change that? If the answer is “all of them” with no override, you’re going to end up unhappy. If the answer is “minimal default with per-field control” — that’s the configuration model worth committing to.
See pricing — Workspace Sync is free for up to 10 users, and per-field controls are available from day one on every plan.