How to Create a Contact Group in Gmail (and Share It With Your Team)

To create a contact group in Gmail, open Google Contacts, click Create label, name it, then select contacts and add them with Manage labels. In Gmail, a contact group is a label. To email everyone on it, type the label name in a recipient field. Sharing it with colleagues is a separate step.

Google Contacts has no button to share a single label, so Patronum adds per-label sharing inside your Google Workspace domain with View, Edit or Manage permissions. First, the group itself.

Create the group in four steps

Google’s help page is titled “View, group & share contacts,” and the grouping happens through labels (Google Contacts Help).

1. Open Google Contacts. Go to contacts.google.com, or open it from the Google apps grid in Gmail. Sign in with the account that owns the contacts.

2. Create the label. On the left, next to Labels, click + to open Create label. Type a name, then click Save. Pick something specific, like “Client: Acme.”

In WebWisp’s own Google Workspace account (October 2026), this dialog asked only for a name. There’s no sharing option at this step.

3. Add contacts to it. Tick the box next to each contact you want. At the top, click Manage labels, choose your new label, then click Apply. To grab everyone, tick any one box, then use Selection Actions and choose All.

4. Check the label. Click the label in the left menu. You should see only the people you added. If someone’s missing, they probably weren’t ticked when you clicked Apply.

That label is now your Gmail contact list for that group.

Email the group: To or Bcc?

In Gmail, click Compose. In the To field, start typing the label name, then pick it from the list. Gmail expands the label into every member’s address (Google Contacts Help).

Before you send, decide which field the group belongs in:

• To or Cc suits people who work together, like a project team. Recipients can see each other; Google notes that anyone in Cc “will see the other recipients of the message.”
• Bcc suits unrelated contacts, like a client announcement. “People you add in ‘Bcc’ can’t see the name or email address of anyone else you add in the ‘Bcc’ field,” and if someone hits Reply all, Bcc recipients “won’t see the reply” (Gmail Help). Put your own address in To. Google’s steps only describe typing a label in To, so if the label doesn’t expand in Bcc, add it in To first, then drag the expanded addresses into Bcc.

One catch. For each contact, “only their default email address is added to the label group.” If a client has a work and a personal address, only the default one gets the email. Check before you send anything important.

Contact label vs Google Group

A Gmail distribution list can mean either of two things, and they behave differently.

A contact label is a personal list in your own Google Contacts. Nobody else sees it, and each message goes out with members’ individual addresses.

A Google Group has its own address, so people can “email each other using a group email address” (Google Groups Help). Anyone can write to that one address, and membership is managed in the group, not in your contacts. On a work or school account, you can choose whether to allow people outside your organization to become members, if your admin has enabled it.

You want	Use
A personal list you email from time to time	Contact label
One address, like sales@, that reaches a team	Google Group
A list several colleagues can see and edit	A shared label (see below)

Can you share a contact group?

Not on its own, natively. We found no Google documentation of a way to share one label. Google’s built-in option is contact delegation, which shares your whole contact list with colleagues in the same domain, works on a computer only, and needs your admin to turn on contact sharing first (Google Contacts Help). In the same account, the delegate dialog reads: “Delegates can view, delete, and create contacts. They can also see some personal info from your Google Account.” Fine for an assistant covering a manager; too much for “share the supplier list with purchasing.”

For the full comparison of export and import, delegation, Directory contacts and label sharing, see how to share Google Contacts with other Gmail users.

Sharing one label with Patronum

Patronum shares a user’s contact label with other people in the same domain at one of these levels (Patronum Help):

• Can View: “Users can only view contacts, they will not be able to edit contacts.”
• Can Edit: “User can view and edit, but can not share contacts with others.”
• Can Manage: full access, including resharing to other users.

Users share through Patronum and its Contact Sharing Chrome extension. Admins can share any user’s label from Patronum’s Contacts section. A policy can share a label automatically with everyone in an organizational unit or Google Group it targets, so new starters get it without asking (Patronum Help). Choosing between Patronum and other add-ons? See shared contacts for Gmail: native options vs add-ons .

Where people get this wrong

Expecting the label to follow the person. A label lives in one person’s Google Contacts. When Google lists the data a super admin can transfer while deleting a user, contacts aren’t on it (Google Workspace Admin Help). Move the list before the account goes.

Using Domain Shared Contacts for colleagues. That feature is for external contacts. Your colleagues are already in the Directory, so adding them again creates duplicates (Google Developers).

Putting a client list in To. Every client sees every other client’s address. Use Bcc.

FAQ

Can I share a Gmail contact group with someone outside my company?
Not as a live list. Delegation is same-domain only, and so is Patronum’s label sharing. Adding people to your Directory as shared external contacts doesn’t help: it shows outside people’s details to your staff, but gives an outside collaborator no access to your list. You can export the list and send the file, but it won’t stay in sync. Some add-ons say they share across organizations; the shared contacts comparison covers them.

How many contacts can a Gmail contact group hold?
Google doesn’t publish a per-label limit or a limit on the number of labels. The account limit is 25,000 contacts or 20 MB, not counting photos (Google Contacts Help).

Check your group before you rely on it

• The label in the left menu shows the number of people you expect.
• Each member’s default email address is the one you want to reach.
• A test email to the group, sent from the field you chose (To or Bcc), arrives with the recipient list you intended.
• If you shared it with Patronum: a recipient can see the label at the right permission level. For Can View, Patronum recommends installing the Chrome extension to prevent editing. If a policy shares it, check a user in the target OU or Group after the policy has run.

To share labels with OUs or Google Groups by policy, see Patronum’s Google Contacts sharing.

Sources

• Google Contacts Help: View, group & share contacts – create label, Manage labels, Selection Actions, default email only, emailing a group
• Gmail Help: Send or unsend Gmail messages – Cc and Bcc visibility, Reply all
• Google Groups Help: Create a group – group email address, members outside your organization
• Google Contacts Help: Contact limits – 25,000 contacts or 20 MB
• Google Contacts Help: Give another user access to your contacts – delegation, same domain, computer only, admin must enable
• Google Workspace Admin Help: Delete or remove a user – data transferable on deletion
• Google Domain Shared Contacts API overview – external contacts only, duplicate warning
• Patronum Help: Sharing Google Contacts (administrator) – permission levels, admin sharing
• Patronum Help: Sharing Google Contacts via a policy – automatic sharing by policy, Chrome extension for view-only
• Patronum Help: Sharing Google Contacts (user) – per label, same domain, Chrome extension

---

Writer notes (not for publishing):

Revision changes (14 Oct):
– Added “Email the group: To or Bcc?” with Gmail Help quotes on Cc and Bcc visibility (verified live 13 Oct 2026). Google’s own steps only document typing a label in To; added a first-hand test placeholder to confirm label expansion in Bcc before publishing.
– Rewrote the external-sharing FAQ: the Directory shows outside people’s details to your staff and gives an outside collaborator no access to your list. Points to export (copy) and to slot10 for cross-organization add-ons.
– Delegation cut to one paragraph, with a link to slot00 for the full comparison; the bulleted delegation limits and the duplicate mobile mistake were removed.
– Added “Contact label vs Google Group” with “Gmail distribution list” and “Gmail contact list” worked in. Google Groups facts verified live on 13 Oct 2026: group email address, and the outside-members option exists only on work or school accounts when an admin enables it.
– Creation remains the main job; Patronum section trimmed (C10 mobile/Outlook sync claim removed, slot10 owns software choice) and linked to slot10.
– “Limits to know” section folded into the FAQ to avoid repeating the limit twice. FAQ cut from four questions to two (dropped labels vs groups and how to share with team, both now answered in the body).
– “Expecting the label to follow the person” now cites Google’s list of data transferable on deletion (contacts not listed) instead of asserting it.
– Ending replaced with a verification checklist; generic “set it up once” CTA removed.
– Not applied: none skipped.
– Patronum fact IDs relied on: C1, C2, C3, C4, C5, C6, C7. Groups worded as policy targets per PF flag 6.
– Re-copy before publishing: Patronum permission quotes and Google quotes.
– Not-yet-published link: /shared-contacts-for-gmail (slot 10) marked LINK LIVE AFTER PUBLISH.
– First-hand tests (13 Oct): used T3 (Labels “+” opens a Create label dialog with a name field only, no sharing option; screenshot img/slot06-contacts-create-label.png replaces the image placeholder; verbatim delegate dialog text added to the delegation paragraph). Still pending: the Bcc label-expansion test and the delegate A-to-B visibility test (both placeholders kept).