How to share Google Contacts with your team

Here is a gap that surprises most Google Workspace admins the first time they hit it: Google Contacts has no share button. You can share a document, a calendar, a drive, even a Chrome tab — but there is no supported way to say “my team should all see this list of customer contacts, kept up to date.”

Google does offer a Directory (the company-wide list of your own employees, managed by admins), but that is not the same thing. The contacts your sales team collects, the vendor list your operations team maintains, the press contacts your marketing team curates — those live in individual personal address books, invisible to everyone else.

This post walks through the workarounds teams typically try, why each one falls short, and how label-based sharing solves the problem properly.

The workarounds and their costs

1. Export and email a CSV

The most common approach: export contacts to CSV, email the file, everyone imports it.

Why it breaks: the moment the file is sent, it is stale. Every recipient now owns an independent copy that drifts as people edit, and re-imports create duplicates. Offboarding is worse — when someone leaves, their copy of your customer list leaves with them, and there is no way to revoke it.

2. A shared spreadsheet

Keeping contacts in a Google Sheet at least gives you one live source. But a spreadsheet is not an address book: contacts do not appear in Gmail autocomplete, do not sync to phones, and cannot be dialed from a mobile contacts app. In practice people copy entries out of the sheet into their own contacts — and you are back to drifting copies.

3. A shared “team” Google account

Some teams create a contacts@company.com account, store everything there, and share the password. This violates most security policies, breaks with 2FA, provides no per-person audit trail, and still does not put the contacts into anyone’s own address book — you have to log in to look things up.

4. Delegation

Google Contacts supports delegation, where you grant another user management access to your contacts. It is designed for the executive-assistant scenario: the delegate manages your contacts in your account. Delegated contacts do not appear in the delegate’s own address book or on their phone, and delegation does not scale to “share this one list with these eight people.”

5. The Directory (admin-managed shared contacts)

Admins can add external contacts to the domain Directory via the Domain Shared Contacts API. This makes them visible in autocomplete for everyone, but it is all-or-nothing (the whole domain sees everything), requires admin tooling for every change, and offers no team-level lists, no roles, and no phone sync of edits by regular users.

What a real solution needs

Stepping back, “sharing contacts with a team” has a concrete definition:

• Contacts appear in each teammate’s own Google Contacts — so Gmail autocomplete and phone sync work.
• There is one source of truth: the owner’s list. Edits propagate; copies do not fork.
• Access is revocable. Unsharing removes the contacts from recipients.
• Roles distinguish people who can look up a number from people who maintain the list.

Label-based sharing: how it works

Rolyio takes the unit of sharing that Google already has — the contact group (what the Google Contacts UI calls a label) — and makes it shareable.

The key design decision: labels in Rolyio are not a parallel structure. They are your real Google contact groups, synced two-way. Create a label in contacts.google.com and it appears in Rolyio; create one in Rolyio and it appears in Google. There is no new place your contacts live — Rolyio stores the sharing relationships and permissions, not a copy of your address book.

Sharing a label looks like this:

1. Connect your Google account at app.rolyio.com.
2. Open the label you want to share and choose Manage access. Domain autocomplete helps you find colleagues and groups.
3. Pick recipients: individual emails, a domain group (expanded into its members), or your entire domain — including accounts created in the future, so new hires get the list automatically.
4. Assign a role: View, Edit, or Can reshare.

After the next sync, each recipient sees a group named “Customers (Shared)” (or whatever your label is called) in their own Google Contacts — and on their phone, since it is a native contact group.

What the roles mean in practice

• View recipients get a read-oriented copy: if they edit a shared contact locally, the owner’s version wins on the next sync.
• Edit recipients are collaborators: contacts they add to their “(Shared)” group flow back into the owner’s label, and their edits sync to everyone.
• Can reshare lets a recipient extend access further — useful for team leads who manage their own group’s access.

Ownership itself is transferable: hand a label to a successor and you are automatically kept on as an Edit collaborator. Details are in roles and permissions.

Revocation actually revokes

When you unshare a label or remove a recipient, the shared contacts are removed from that person’s address book on the next sync. This is the piece no CSV workflow can offer: offboarding someone takes one click, not a hopeful request to delete a file.

Sync cadence

Google does not provide push notifications for contact changes, so Rolyio polls roughly every 60 seconds (there is also a manual Sync contacts button when you want changes through immediately). Deduplication is by email address, so sharing a list with someone who already knows half the people in it does not create duplicates.

Getting started

If your team’s customer list currently lives in a spreadsheet, a CSV attachment, or one long-suffering person’s personal contacts, the migration is short: put the contacts under a label, share the label, and delete the copies. From then on there is one list, everyone sees it in Gmail and on their phones, and access follows people — not files.