Google Workspace gives a small team four ways to share one address, and they are not interchangeable. Gmail delegation suits one person helping another. The native shared inbox, rolling out on Business editions, covers a common address with low volume. Google Groups Collaborative Inbox adds assignment and a completed status, but requires conversation history to be enabled and the right moderation permissions. None of them shows you, in the moment, that a colleague is already writing a reply.
The question small teams really ask
When two, three, or five people need to answer messages sent to the same address, Google Workspace looks like it should already have the answer. You may have Gmail delegation, Google Groups with Collaborative Inbox mode, and a native shared inbox that has been rolling out in phases in the Admin console since late 2025.
Those native tools are useful. They are also easy to misunderstand. A delegated Gmail mailbox is not the same thing as a team workflow. A Google Group configured as a Collaborative Inbox is not the same thing as the familiar mailbox your team already knows.
For a small business, school office, or association, the real question is not “Can Google do this?” The useful question is: can the whole team reply clearly, avoid duplicate answers, keep history, and onboard new people without training everyone on admin concepts?
This article explains the practical difference, then points you toward the right setup.
Option 1: Gmail delegation
Gmail delegation lets one account give another user access to read, send, and delete mail on its behalf. The important point is that each person signs in with their own Google account, not with the shared mailbox password.
That is already much safer than passing one password around. If Marie leaves the team, you remove Marie’s delegation. You do not have to reset the shared mailbox password for everyone.
Delegation works best when the flow is simple: one assistant helps one manager, or a small office checks one mailbox with a low volume of messages. It keeps the mailbox interface familiar, which is a real advantage for non-technical teams. Delegated accounts are also arriving in the Gmail mobile apps on Android and iOS: Google announced the change in late June 2026, and the rollout runs through late July 2026 on iOS, so it may not have reached your account yet.
But delegation does not turn Gmail into a shared inbox tool. It does not give you clean ownership states like “assigned to Julie,” “waiting for client,” or “closed.” It does not show a simple queue where the team can see who is already replying. It also does not give you internal notes attached to the conversation in a way designed for team decisions.
For occasional backup, delegation is fine. For daily team production, it usually becomes a set of informal habits: stars, labels, side messages, and “did you answer this one?” conversations.
Option 2: Google Groups Collaborative Inbox
Google Groups can be configured as a Collaborative Inbox. This mode adds team features around conversations: members can assign conversations, mark them as complete, and use group-level workflows.
That sounds close to a shared inbox, and for some teams it is enough. If your organization already uses Google Groups and your team is comfortable with it, Collaborative Inbox can help structure inbound messages without buying another tool.
The tradeoff is adoption. A Collaborative Inbox is not Gmail. It is a group interface with its own concepts. Many small teams do not want a second place to check, a new workflow to remember, or admin setup that only one person understands.
There is also a communication style issue. Schools, TPEs, and associations often need a mailbox-like experience, not a ticketing or forum-like experience. They want to open the shared address, see messages, assign them, write notes, and reply from the usual identity.
If your team says “we just need our contact@ mailbox to work together,” Collaborative Inbox can feel more like infrastructure than a daily tool.
Option 3: the native shared inbox (rolling out since late 2025)
Google Workspace now offers a native shared inbox, rolling out in phases since late 2025 and reaching more tenants through 2026. An admin creates it from the Admin console, under Home > Users > “Set up a shared email address”. It is available on the Business Starter, Business Standard, and Business Plus editions, but not in every tenant yet: if you do not see it in your Admin console, Google’s own advice is to use delegated Gmail accounts in the meantime.
Here is what it does. Each member opens the shared mailbox with their own Google account. Members can read, send, and delete messages and manage the mailbox’s contacts. When someone replies, the recipient sees the shared address as the sender, with a “sent by” line naming the teammate who wrote it. Admins get two settings: how “mark as read” behaves across members and whether sender information is displayed.
That is real progress: no shared password, one common address, visible attribution. Under the hood, it is Gmail delegation with a simpler setup, and it inherits delegation’s limits.
What it still lacks for a team: per-conversation assignment, an open or done status, internal notes, and any warning when two people answer the same message at once. The telling detail: Google’s own Collaborative Inbox in Groups does offer assignment and resolution states. The new shared inbox does not.
It is enough for two or three people with low volume, as long as saying “I’ll take this one” out loud still works. Once volume grows or replies carry weight, the four problems below come right back.
Where native Google tools start to break down
Native options usually fail for small teams in four places.
First, ownership is not visible enough. If an email is important, someone must clearly own it. Without explicit ownership, everyone assumes someone else will reply.
Second, collision protection is weak. The embarrassing case is simple: Paul and Julie both open the same request and both start replying. Unless your tool clearly warns them, the customer may receive two answers.
Third, internal context gets scattered. Teams discuss emails in chat, by forwarding, or by walking to the next desk. The decision disappears from the original thread. Two months later, nobody remembers why that reply was sent.
Fourth, onboarding is harder than expected. When a volunteer, secretary, or part-time teammate joins, you need them to understand the state of the mailbox quickly. Informal labels and hidden rules do not travel well.
These problems are exactly why the complete shared inbox guide starts from responsibility and continuity, not from provider features.
When Trupeo is the simpler answer
Trupeo is useful when you want to keep your Google Workspace mailbox but make it usable by a team.
The new native shared inbox fixes the password problem. It still cannot tell you who owns a message, and it keeps no trace of why the team replied the way it did.
You connect the existing address. Every teammate gets their own access. Incoming emails appear in one shared workspace. The team can assign messages, add private notes, tag conversations, and see when someone else is already replying.
That last point matters. A small team does not need more dashboards. It needs fewer mistakes. Collision detection and clear ownership prevent the daily friction that native mailboxes leave to discipline.
The result is simple: Google Workspace keeps doing email delivery. Trupeo adds the team layer that Google Workspace was not designed to provide for small, non-technical teams.
For budget-sensitive teams, the question is also practical. If you are comparing tools, read Trupeo vs Gmail shared mailbox and then check our pricing. If you are a small business, the small-business page explains the use case without enterprise support jargon.
Quick decision guide
Choose Gmail delegation if one person occasionally helps another person with a mailbox.
Choose the native shared inbox if your Business edition already shows it, your volume is low, and a common address with “sent by” attribution covers your needs.
Choose Google Groups Collaborative Inbox if your team already works inside Google Groups and accepts that workflow.
Choose Trupeo if several people answer a shared address every day and you want visible ownership, internal notes, collision detection, and a familiar mailbox experience.
The best tool is the one your team will actually use. For most small teams, that means fewer concepts, not more.
Frequently asked questions
Does Google Workspace have a shared inbox?
Yes, in several forms that do different things. A native shared inbox is rolling out on Business editions. Before that, the two established routes were Gmail delegation, where someone opens another mailbox from their own account, and a Google Group with Collaborative Inbox enabled, which adds assignment and a completed status on top of a mailing list.
What is the difference between Gmail delegation and a Collaborative Inbox?
Delegation gives access: the delegate reads, sends and deletes in the mailbox from their own account, with no notion of who owns which message. A Collaborative Inbox adds coordination: taking a conversation, assigning it, and marking it complete, no action needed or duplicate. It is a group rather than a mailbox, and it needs conversation history turned on to work at all.
How many delegates can a Gmail account have?
A work or school account allows up to 1,000, though Google notes that with typical use, 40 delegates can access a Gmail account at the same time. A personal @gmail.com account is capped at 10.
Does the recipient see who replied?
With Gmail delegation, yes: when a delegate sends, their own email address appears. That is fine internally and often unwanted on a customer-facing address, where you want the reply to come from the shared address itself.
Which option should a three-person team pick?
If one person owns the address and others help occasionally, delegation is enough. If all three answer daily and need to know who is handling what, none of the native options gives you an owner per message with internal notes and a signal that someone is already replying, which is where a shared inbox on top of Gmail becomes the simpler answer.
Sources:
- Create a shared inbox: official documentation for the native shared inbox: editions, setup, permissions, and phased rollout.
- Delegate and collaborate on email: official explanation of Gmail delegation and delegate access.
- Use a group as a Collaborative Inbox: assignment, completion, and conversation status features in Collaborative Inbox.
- Work with delegated Gmail accounts from mobile devices: official June 2026 announcement of the phased rollout of delegated accounts in the Gmail mobile apps.