Google Collaborative Inbox: setup, limits, and the settings that break it

You switched the Collaborative Inbox on, told the team the support address now has a queue, and a week later you are the only person who has ever assigned anything. Everyone else reports that assignment does not work for them. Nothing in the group settings looks wrong, and the obvious conclusion is that the feature is broken.

It is not. Google puts the Collaborative Inbox actions behind two group permissions that are separate from the feature itself, and switching the feature on grants neither of them. Whoever created the group is an owner and gets there by another route, which is why the failure looks so much like favouritism. This page covers the setup path, the two permissions that decide whether any of it works, the five things that surprise teams in the first week, and the ceilings Google publishes so you can tell arithmetically when the address has outgrown a Group.

The short version

• A Collaborative Inbox is an ordinary Google Group with one extra setting switched on. It gives an address an assignee and three resolution states instead of just broadcasting to members.
• Conversation history has to be on first. Until it is, Collaborative Inbox features cannot be enabled at all.
• The actions sit behind two different permissions, both under Group settings > Posting policies. Take, assign, reassign, drop and mark complete need Who can moderate metadata. Mark as duplicate and mark as no action needed need Who can moderate content.
• Your own test message will not arrive. Gmail does not deliver mail you send to a group you belong to into your own inbox, and that fact accounts for a lot of false alarms.
• The archive lives and dies with the group. Deleting the group deletes its messages, and that happens even when the group is under a retention rule or a legal hold.

What a Collaborative Inbox actually is

A Collaborative Inbox is a Google Group with one setting switched on, which turns a broadcast address into a queue: every conversation gets an assignee and a resolution state. There is no separate product to buy or provision. A plain group hands the mail to every member and then forgets about it. With the feature on, a conversation can be taken or assigned to a named person, then marked complete, marked as a duplicate of another conversation, or marked as needing no further action. Members can filter the list down to whatever is still unresolved.

That is genuinely most of what a small team needs from a support address, and it costs nothing beyond the Workspace licences you already pay for. If you are still deciding whether a group is the right shape at all, the difference between a plain mailing list and a mailbox a team works out of is the decision underneath this one. Settle that first. Collaborative Inbox is also only one of several ways to run a shared address on Google's platform: the other Gmail routes are covered separately. For the wider version of the problem, and what teams typically do at each stage of it, start with the guide to how shared inboxes work as a category.

Turning it on, and the setting that has to come first

Two prerequisites, then four clicks.

Conversation history has to be on. Google's setup page is unambiguous about the order: "To enable Collaborative Inbox features, you must turn on conversation history." Try it the other way around and the feature will not enable. That is the whole explanation for an option that refuses to stay switched on, and it sends a fair number of people looking at Workspace edition upgrades they do not need.

You have to be an owner or a manager of the group. A plain member cannot switch it on, no matter how senior they are elsewhere in the company.

With both in place, follow Google's instructions for turning on Collaborative Inbox features: sign in at groups.google.com, click the name of the group, click Group settings on the left, and under Enable additional Google Groups features, select Collaborative Inbox.

One dependency sits above all of this and belongs to your Workspace admin. Groups for Business has to be switched on for the domain. If an admin turns it off, Google's administrator FAQ says the groups themselves survive: they "remain active, but the groups won't have any of the advanced features available with the Groups for Business service", and re-enabling the service restores the settings. So a Collaborative Inbox that quietly reverted to a plain mailing list is a question for the admin console. You will not fix it from inside the group.

Why assignment does not work: the two permissions

Enabling Collaborative Inbox creates the queue. It does not decide who is allowed to work it. Six actions are governed by two unrelated group permissions:

Both live in the same place: Group settings > Posting policies, where Google documents the group permission list. Set Who can moderate metadata to the people who answer mail, and the assignment half of the feature starts working for them. Set Who can moderate content as well if you want the duplicate and no-action markers used by anyone other than owners.

Google is looser about this elsewhere than the table suggests. That same permissions page describes Who can moderate metadata as covering "categorizing content and all Collaborative inbox features", which reads as though one setting governs everything. The action-level documentation is the precise version, and it splits the six actions across the two permissions as above.

There is also a diagnostic worth knowing, because it is the pattern almost every team hits. If assignment works for the person who created the group and for nobody else, stop looking at the feature and look at these two settings. Group creators are owners, and they reach the actions through the owner role rather than through a permission anyone thought to grant.

If the permission is set correctly and taking a conversation still does nothing, check what kind of group you are actually in. Google's page on fixing common group settings issues names a cause that is easy to miss: "The take and assign conversations function exists only for Collaborative Inbox groups. Even if your users are able to moderate metadata, they will not be able to take or assign conversations for any other group type except for Collaborative Inbox." A team that granted the permission on the wrong group, or on a group where the feature was never enabled, gets exactly the symptom this page opened with.

Once that is sorted, Google's page on taking and assigning conversations gives the real paths. To take one, open the conversation and click Take. To hand it to someone, open it, click Assign, enter their email address and click Done. Drop puts it back in the unassigned pile.

Then there is the multi-select route. It is what makes a morning triage pass bearable, and it saves opening every conversation one at a time: point at a conversation in the list and check the box next to the poster's name. Check as many as you like, then use Take, Assign or Drop at the top of the list to act on all of them at once.

Five things that surprise teams in the first week

Your own test message never arrives. You switch the feature on, email the group address from your own account to check it works, and nothing lands. Google documents this exactly: "Gmail doesn't deliver messages that you send to your own alias (or to a Group you belong to) to your inbox." The message is not lost, it is in your Sent Mail and All Mail. Google's troubleshooting page for this suggests setting the group up as a "Send mail as" address if you want your own messages to it to appear. Until then, test from a personal account or ask a colleague outside the group.

Replies still go out from personal addresses. Turning on a Collaborative Inbox does not change what a customer sees in the From line. To answer as the group, each member has to add the group address under Gmail's Send mail as settings, and a work account adds a wrinkle: Google's instructions note that to receive the verification email for a group alias you have to give delegates access to the group, and you need access to the group's permissions to change that for anybody else. Worth doing on day one, because the alternative is a customer replying to an individual employee and the thread leaving the queue entirely.

Everything happens at groups.google.com. Every Collaborative Inbox action Google describes lives in the Groups interface, not in Gmail. The mail still reaches members' inboxes, but taking, assigning and resolving are done in a separate tab. For a team that lives in Gmail all day, that context switch is the real daily cost of the free route.

Shared labels can be deleted by anyone. Labels replaced the old tags and categories, and they are shared across the group rather than personal. Google's page on labels sets out the consequences plainly: the shared labels feature has to be enabled first, applying a label needs the Who can view conversations permission, and "when shared labels are on, any group member can create or delete labels". Any member can delete your taxonomy on a Tuesday. Label names also cannot contain spaces or a long list of punctuation, so plan for refund-request rather than Refund Request or refund/request.

Marking a duplicate locks the thread. It is more final than it looks. Google's Collaborative Inbox documentation states that "marking a conversation as duplicate locks the conversation so that you can't perform any actions on it". The constraints are specific: both conversations have to be in the same group, and neither can already be part of a duplicate pair.

What it does not do, and what it used to do

The rebuild history is worth a paragraph, because people who used classic Groups remember losing things. The feature was not retired, it was rewritten, and Google publishes the list of what did not survive: using tags and categories to manage content is gone, replaced by labels; moving a topic from one group to another is gone; and so is letting people change their messages after posting them. If a process you inherited depended on any of those, it is not coming back.

What it never had is the reporting layer: no response-time targets, no automatic routing, no measurement of how long anything took. The section below turns those gaps into the specific triggers that tell you the address has moved past what a Group can do.

The limits Google publishes

The numbers are the fastest way to tell whether you are near an edge, and Google's Groups policies and limits page carries them:

Read that table honestly and it says something reassuring. Almost none of these is what stops a small support team. Members are unlimited, and no five-person team is anywhere near 3,600 group memberships. The one a real address can meet is the inbound rate: 300 emails per group per five minutes, which a bulk notification or an angry mailing list can produce without trying. When you do hit a limit, Google says the account's activity is temporarily restricted, and restrictions "typically last an hour but can last as long as 24 hours".

The archive, and the way out

For a support address with any kind of compliance obligation, this is the most important section on the page.

A group keeps everything. The administrator FAQ linked above puts it in one line: "A group's conversation history never expires, so messages remain in there until the group is deleted." Two or three years in, that archive is a real asset. It is also entirely dependent on the group continuing to exist.

Google Vault can retain, hold and search those messages, with retention periods anywhere from 1 to 36,500 days, but the Vault documentation for Groups fences it in three ways that matter. Only messages sent while conversation history was turned on are covered, so history that was off is simply not there to retain. Messages sitting in a moderation queue waiting for approval are not retained at all. And linked files are outside the scope, even though attachments are inside it.

Then the sentence to read twice: "Messages in Groups are deleted even when the deleted group was subject to a hold or retention rule." Deleting the group deletes the mail, holds included.

Two practical consequences. Turn conversation history on before you need the archive, because it does not work retroactively. And never let deleting the group be part of anybody's cleanup plan, including the plan for the day you move the address somewhere else.

When the queue has outgrown it

The trigger is never "we outgrew the features". It is one specific thing you needed and could not have. Any of these means the free route has run out:

• You need to give a customer a reference number they can quote back to you.
• You need a clock on a thread while it is open, and a report on it afterwards.
• You need mail to route itself to the right person instead of waiting for someone to assign it.
• You need to see that a colleague is answering a message right now, before you answer it too.
• You need the archive to outlive the group.

Before you spend anything, though, the working practices a shared queue needs are free and fix a surprising share of the symptoms people go shopping for. And if the reference number and the status field are what you are really after, what changes when a message becomes a ticket covers that direction properly. If you are unsure whether the number of people answering still matches the volume arriving, the support team size calculator does that arithmetic.

If two or more of those triggers are true, the conversation stops being about Google's settings. A dedicated shared inbox tool such as TriageFlow puts an owner on a message before anyone opens it and keeps the response clock running where the team can see it. No group permission produces either of those.

Frequently asked questions

What is the difference between a Google Group and a Collaborative Inbox?

They are the same object. A Collaborative Inbox is a Google Group with one additional setting enabled, which adds an assignee and the resolution states to conversations that would otherwise just be broadcast to members. You do not create a different kind of group; you change a setting on the one you have.

Why is the Collaborative Inbox option greyed out?

Because conversation history is off. Google requires history to be on before Collaborative Inbox features can be enabled, so until a group owner or an admin turns it on, the option will not take effect. Check that first.

Why does nothing happen when I click Assign?

The queue exists but the permission to work it has not been granted. Assigning is governed by Who can moderate metadata, under Group settings > Posting policies, and enabling Collaborative Inbox does not set it. If the feature works for the person who created the group and for nobody else, that is the setting to open.

Is Google Collaborative Inbox free?

There is nothing extra to buy: it is a setting on a Google Group, so it comes with the Workspace licences you already have. The one dependency is Groups for Business being switched on for your domain, and that lives in the admin console.

Can I reply from the group address instead of my own?

Yes, but each person has to set it up individually by adding the group as a "Send mail as" address in their Gmail settings. Getting the verification email for a group address needs delegate access to the group, so set everyone up as one batch job when you build the queue.

How do I assign several conversations at once?

Point at each conversation in the list and check the box next to the poster's name, then use Take, Assign or Drop at the top of the list. It applies to everything selected.

Does Collaborative Inbox work inside Gmail?

The mail itself arrives in members' inboxes like any other group message. The queue does not: every Collaborative Inbox action Google documents (take, assign, drop, complete, duplicate, no action needed) is described in the Groups interface at groups.google.com, so the triage half of the work happens in a separate tab from the mail.

Bottom line

If assignment only works for one person, the fix is two settings deep: conversation history on, then Who can moderate metadata opened up to the people who actually answer mail. Do those, add the group as a send-as address for everyone on day one, and a Collaborative Inbox will carry a small team a long way for nothing. The decision to move on eventually will come down to one of the five triggers above, and almost certainly not to running out of members.