Patronum Logo
00%
Patronum Logo
menu-icon

Google Groups Collaborative Inbox: Setup, Limits and When to Use It

By Patronum

November 06, 2026

Read Time: 6 mins

A Google Groups collaborative inbox is a normal group with tracking switched on, so the people who answer support@ or sales@ can take, assign and resolve each conversation instead of all replying (or nobody replying). You turn it on per group in Google Groups after turning on conversation history, and it needs Groups for Business switched on. It suits a small team with modest volume. If customers need to write in, check two separate settings: one for the admin, one for the group.

Haven’t created the group yet? Start with how to create a Google Group email address , then come back here.

What does a collaborative inbox add to a normal group?

A plain Google Group distributes mail to its subscribed members, according to each member’s subscription setting, and nothing shows who’s dealing with a message. Collaborative Inbox adds an assignment workflow. Members with the right permissions can:

  • Take a conversation they’ll answer themselves
  • Assign it to someone else. The assignee gets an automated email, including any note you add
  • Drop an assignment, whoever made it
  • Mark it complete, duplicate or no action needed
  • Search by assignee or resolution status, for example “Assigned to me”

All of this happens in the group’s conversation list at groups.google.com. A copy of the mail in someone’s Gmail doesn’t show that anyone has taken responsibility.

It’s a feature you switch on for one group, not one of the four access types of Google Groups. For the wider choice between a group, a delegated account and a help desk, see Google Groups vs a shared mailbox.

Which Google Workspace editions include it?

Collaborative Inbox depends on the Groups for Business service, and Google’s Groups for Business pages don’t list an edition restriction. What matters is whether the service is on. When it’s off, Collaborative Inbox isn’t available and users can’t create groups in Google Groups.

To turn it on, an admin with the Groups for Business administrator privilege goes to Menu > Apps > Google Workspace > Groups for Business, clicks Service status, and chooses On for everyone (or turns it on for specific organizational units). Google says changes can take up to 24 hours. If your responders sit in several OUs, check each one.

How do you turn on a collaborative inbox?

You need the Owner or Manager role on the group. At groups.google.com:

  1. Open the group and click Group settings, then Posting policies. Under Conversation history, select On and save. Google requires this before Collaborative Inbox features work.
  2. Go to Group settings > General. Under Enable additional Google Groups features, select Collaborative Inbox, then click Save changes.
  3. Set who can take and assign conversations (next section).
  4. Optional: under Posting policies, set Default sender to Group address. Google describes this choice as best for groups where many people respond on behalf of the group, such as product support, so replies don’t come from each author’s own address.

Who can assign and resolve conversations?

Owners and managers grant these with permission sliders in Group settings:

TaskPermission Google lists
Take, assign, drop, mark completeWho can moderate metadata
Mark duplicate or no action neededWho can moderate content (Google’s setup page also lists Who can moderate metadata)
Read conversations and search “Assigned to me”Who can view conversations

If everyone triages, give Who can moderate metadata to group members. If one lead dispatches work, keep it with managers. Because Google’s pages disagree on duplicates, give whoever cleans them up both moderate permissions.

One detail catches mixed groups: if a group has external members and you set a permission to Entire organization, Google says those external members don’t receive it.

Can customers email a collaborative inbox?

Only if two settings allow it. Customers don’t have to be group members to write in; posting from outside and adding external members are separate settings.

In our test organization, when we walked through Create group at groups.google.com on November 5, 2026 (without saving), the Who can post slider offered Group owners, Group managers, Group members and Entire organization. No option for people outside the organization appeared at that step.

Google Groups create group step 2, privacy settings, with Who can post set to Entire organization
Step 2 of creating a group in our test organization: the posting slider stops at Entire organization. Captured November 5, 2026.

Existing groups may already be open, so check both layers before you publish the address:

  1. Admin level. In the Admin console, go to Menu > Apps > Google Workspace > Groups for Business > Sharing settings. Look for Group owners can allow incoming email from outside the organization. It’s unchecked by default, and while it stays unchecked, group owners can’t allow outside mail at all.
  2. Group level. In Google Groups, open the group, go to Group settings > General, and check Who can post. For customers, it needs to be Anyone on the web. Click Save changes if you changed it.

The admin setting only gives owners the choice, so finance-approvals@ can stay closed while support@ opens up.

Worried about spam? Posting policies > Message moderation can hold non-members’ messages for review, but then every customer email waits for a moderator first.

What are the limits of a collaborative inbox?

These come straight from Google’s help pages:

  • Take and assign exist only in Collaborative Inbox groups.
  • Marking a conversation as a duplicate locks it, so no further actions are possible. You can only mark it as a duplicate of a conversation in the same group.
  • Deleting resolved conversations is permanent. Google suggests filtering to unresolved conversations instead.
  • A conversation that’s already assigned stays assigned when you mark it no action needed.

Google’s pages don’t describe shared drafts, response-time targets or reporting for collaborative inboxes. If your team needs any of those, test them in a pilot group before you commit.

When should you use a delegated mailbox or a help desk instead?

Keep the collaborative inbox while “who’s got this one?” is the main problem. Move on when:

  • The team would rather work in Gmail. With Gmail delegation, each person opens a dedicated account from the profile menu in their own Gmail. Google allows up to 1,000 delegates on a work or school account but says about 40 can access it at once with typical use, fewer with heavy use; check Gmail Help before you plan around it.
  • You need targets, reporting or customer history. That’s help desk territory.
  • You only need one address to reach several people, with no tracking. A plain group does that. An alias doesn’t: it’s an extra address on an existing user or group, so mail simply lands wherever that account’s mail goes. See email alias vs group vs delegation.

Where Patronum fits

A collaborative inbox is only as good as its member list. Patronum, a Google Workspace management tool, keeps that list current through onboarding and offboarding policies:

  • Membership by policy. An onboarding policy’s Group section can add users to Google Groups based on organizational unit, group or directory attributes, and Patronum keeps the group’s membership in sync with the policy.
  • Leavers. An offboarding policy can remove the user from Google Groups and transfer group ownership, so the inbox doesn’t end up owned by a suspended account.
  • A leaver’s address into the team inbox. An offboarding policy can rename the user and then assign their old address to a Google Group. The group must already exist; the policy can’t create it.

Policies run once you activate them, on the next scheduled cycle (hourly by default). After the first run, check the group’s member list in Google Groups. For the full leaver sequence, see the Google Workspace offboarding guide.

Putting it together: a six-person support team

Say a 150-person company has six people answering support@ by forwarding mail to each other. Here’s the setup:

  • Groups for Business shows On for every OU the six responders sit in
  • Conversation history is On for support@
  • Collaborative Inbox is selected under Enable additional Google Groups features
  • The six have Who can moderate metadata; the team lead also has Who can moderate content
  • The admin has checked Group owners can allow incoming email from outside the organization, and support@ has Who can post set to Anyone on the web
  • Default sender is set to Group address, if replies should come from support@
  • A test email from a personal Gmail account arrives, one responder clicks Take in Google Groups, replies, and marks the conversation complete

If the test message never arrives, recheck the two posting settings first.

Sources