How to Create a Shared Mailbox in Google Workspace 2026

Quick Answer

Google Workspace does not offer a dedicated shared mailbox feature the way some other platforms do. Instead, teams create one using either Gmail delegation, which lets multiple people access an existing mailbox, or a Google Groups collaborative inbox, which creates a dedicated group email with assignment and status tracking features. Both are included with any Google Workspace plan at no extra cost.

A shared mailbox in Google Workspace is not a single built in feature, which surprises people coming from platforms that offer one directly. Instead, Google Workspace gives you two different ways to let multiple people manage one email address: Gmail delegation, where an existing mailbox owner grants access to teammates, and Google Groups collaborative inbox, where a dedicated group email is created with built in assignment and status tracking. Neither requires extra licensing beyond your existing Workspace plan. This guide covers how each method actually works, their real limits, which one fits which team size, and where both eventually fall short for high volume support operations.

Word count: 111 words. Primary keyword in line 1. Semantic entities: Gmail delegation, Google Groups, collaborative inbox, assignment tracking, Workspace plan. Evergreen language: yes.

What a Shared Mailbox Means in Google Workspace

Google Workspace does not have a single feature literally called a shared mailbox. It offers two different mechanisms that accomplish the same practical goal: letting more than one person send, receive, and manage email from a common address. The two are not interchangeable. They differ in setup, features, and how many people can realistically use them at once.

Gmail delegation works by having an existing mailbox owner explicitly grant access to other users, similar to giving someone a key to your own inbox. Google Groups collaborative inbox instead creates a new, dedicated group email address that members access through the Groups interface, with features built specifically for divided team workflows like support or sales queues.

Method 1: Gmail Delegation

Gmail delegation is the simpler of the two options, and it’s the better fit when a small number of people need access to what is effectively one person’s or one role’s inbox.

How to set it up:

1. Sign in to the Gmail account you want to delegate access to.
2. Go to Settings, then See all settings, then the Accounts tab.
3. Under “Grant access to your account,” click Add another account.
4. Enter the delegate’s full email address and confirm.
5. The delegate receives an invitation email. It can take up to 24 hours before they can actually access the account.

Once accepted, delegates can read, send, reply to, and archive email on behalf of the account, and they can also view and manage contacts. When a delegate sends a message, it shows the account owner’s address, with the delegate’s own address typically visible depending on your organization’s settings.

The real limits, precisely. Google’s own documentation states a single account supports up to 1,000 configured delegates through the standard Gmail and Admin console interface. That number is higher than most teams will ever need, but it isn’t the practical ceiling. Google explicitly recommends no more than 40 people accessing the same delegated account concurrently to avoid performance issues, and heavy automated use by even one delegate can reduce that further. Separately, if delegates are managed through the Gmail API rather than the standard interface, the technical limit drops to 25 delegates per account, a detail that matters if you’re provisioning access programmatically rather than through the admin console.

What delegation does not include. There’s no collision detection, meaning two delegates can open and start replying to the same email without any warning that someone else is already on it. There’s also no way to formally assign a specific email to a specific person, no internal notes visible only to the team, and no built in reporting on response times or volume.

Method 2: Google Groups Collaborative Inbox

A collaborative inbox is a purpose built setting inside Google Groups, designed specifically for teams that need to divide and track incoming email rather than just share access to one mailbox.

How to set it up:

1. In the Admin console or at groups.google.com, create a new group and give it the address you want, such as support@yourdomain.com.
2. In the group’s settings, go to Information, then General, and set the group’s purpose to Collaborative Inbox.
3. Add team members to the group.
4. Configure who can post, join, and view conversations under the group’s Permissions settings.
5. Once enabled, members access the shared queue through Google Groups rather than a standard Gmail inbox.

What it adds beyond delegation. Members can mark a conversation as Complete, Duplicate, or No Action Needed, assign a conversation to a specific person, leave notes visible only to other group members, and filter the queue by status or assignee. This is a meaningfully different workflow from delegation, closer to a lightweight ticketing system than a shared inbox in the traditional sense.

Where it still falls short. Collaborative Inbox still lacks true collision detection in the sense of a live warning while someone is actively typing a reply. Reporting is basic compared to a dedicated helpdesk tool, and the interface is built around Google Groups rather than a purpose built support interface, which some teams find less intuitive day to day than a standard inbox.

Gmail Delegation vs Collaborative Inbox: Side by Side

When Both Options Start Falling Short

For a small team checking a shared inbox occasionally, either method works well and costs nothing beyond your existing Workspace plan. The limits become a real problem at a specific point: once your team is fielding a high enough volume of email that duplicate replies, unclear ownership, or the lack of real reporting start costing meaningful time.

Honest limitation: if your support or sales team is handling more than a handful of conversations a day and needs actual collision detection, SLA tracking, or detailed analytics, a dedicated shared inbox tool that layers on top of Gmail is typically the next step rather than trying to stretch Collaborative Inbox further. This isn’t a failure of Google Workspace, it’s simply a different category of tool solving a more specific problem.

A common pattern is a small team starting with Collaborative Inbox for a support address, which works well until the team grows past roughly five or six people actively replying throughout the day. At that point, the status marking system that worked fine for a smaller group starts requiring more manual discipline to keep accurate, and the absence of true collision detection becomes a more frequent, visible problem rather than an occasional edge case. That’s usually the point worth evaluating a dedicated tool rather than continuing to push Collaborative Inbox past the volume it was designed for.

Security and Access Considerations for Either Method

Sharing access to a mailbox, by either method, expands who can see potentially sensitive email, which is worth thinking through before rolling either option out broadly.

With Gmail delegation, every delegate has full access to the mailbox’s history, not just new messages going forward. If the account has ever received sensitive information, financial details, HR matters, legal correspondence, every delegate can see that history by default. There’s no way to grant a delegate access starting only from a certain date or limited to certain labels.

With Collaborative Inbox, access is scoped to the group itself rather than an individual’s full mailbox, which is a cleaner boundary for a purpose built shared address like support or sales. Group permission settings control who can view, post, and join, and these are worth reviewing explicitly rather than leaving at their defaults, since a misconfigured group can end up more open than intended.

For both methods, removing access when someone leaves the team is a manual step, not automatic. Delegation access needs to be revoked from the Accounts settings, and group membership needs to be removed from the group’s member list. Neither is difficult, but both are easy to forget during offboarding if it isn’t part of a documented checklist, and a former employee retaining access to a shared support or sales inbox after they leave is a common, avoidable gap.

A reasonable default: treat any shared mailbox, delegated or group based, as a resource that needs the same offboarding attention as a user account itself, since functionally it grants ongoing access to communications the same way an account would.

Choosing delegation for a support queue. Delegation works fine for a shared role inbox like a manager and their assistant. It’s a poor fit for a support queue with multiple people replying to different customers throughout the day, since there’s no way to track who is handling what.

Assuming Collaborative Inbox eliminates duplicate replies. Status marking reduces the odds of two people replying to the same thread, but it depends on people actually using it consistently. It is not the same as a live lock that prevents a second reply outright.

Not setting clear posting and access permissions on the Group. Leaving a Collaborative Inbox group’s permissions at their default setting can allow broader access or posting rights than intended. Review these specifically during setup rather than leaving them unconfigured.

Conclusion

A shared mailbox in Google Workspace comes down to choosing between two genuinely different tools rather than one universal feature. Gmail delegation is simple and works well for a small, shared role inbox. Collaborative Inbox adds real assignment and status tracking that fits a support or sales queue better, though it still stops short of a dedicated helpdesk tool once volume grows. Leads Monky is an authorized Google Workspace reseller serving 1,000+ companies across the USA, UK, UAE, Pakistan, and India, and can help configure either setup correctly during onboarding. Visit Google Workspace Official Page to see current plans.

FAQs

Does Google Workspace have a true shared mailbox feature?

Not as a single named feature. It offers Gmail delegation and Google Groups collaborative inbox, two different built in methods that both let multiple people manage one email address without a dedicated shared mailbox product.

What is the difference between collaborative inbox and shared mailbox?

Collaborative inbox is Google’s specific feature inside Google Groups, with assignment and status tracking. Shared mailbox is a general term that can describe either Gmail delegation or a collaborative inbox, since Google Workspace doesn’t have one dedicated feature by that exact name.

How many delegates can a Gmail account have?

Up to 1,000 through the standard Gmail and Admin console interface, though Google recommends no more than 40 concurrent users for performance. The limit drops to 25 if delegates are managed through the Gmail API instead.

Can Gmail delegation and collaborative inbox be used together?

They serve different purposes and are typically chosen separately rather than combined for the same address. A team usually picks whichever fits their workflow, delegation for a simple shared inbox, collaborative inbox for a tracked queue.

Is a shared mailbox included in every Google Workspace plan?

Yes. Both Gmail delegation and Google Groups collaborative inbox are included at every Google Workspace tier, from Business Starter through Enterprise, at no additional licensing cost.

What should I use if my team outgrows both options?

Once your team needs true collision detection, SLA tracking, or detailed reporting, a dedicated shared inbox or helpdesk tool built to layer on top of Gmail is typically the next step rather than pushing Collaborative Inbox past what it’s designed for.