Your support@ inbox has a way of losing things. Someone assumes someone else answered the customer. A refund sits for three days because nobody claimed it. A contract gets forwarded with “FYI” and disappears into the void.
If that sounds like your support@ address, a shared mailbox can fix most of it. And it’s easier to set up than most people think
In this guide, you’ll learn:
- What a shared mailbox is, and how it differs from a distribution list
- How to add a shared mailbox in Outlook on Windows, Mac, and the web
- How to set up a shared inbox in Google Workspace, including Collaborative Inbox
- The security gaps most teams miss, including the one permissions can’t fix
- When shared inbox software is worth paying for, and when it isn’t
- Which providers keep your team’s messages unreadable to everyone else
- How to activate mailbox sharing in Mailfence
What is a shared mailbox and who uses one?
A shared mailbox is one email address that several people can open, read, and send from, each using their own login. Nobody signs in to the mailbox directly. Access is granted per person, and the mailbox appears alongside each user’s own folders.
It behaves like a normal email account, except several people manage it. That makes it a common way to run generic info@ or support@ addresses, or to hand your own mail to an assistant.
Any team where the address matters more than the person behind it: support, sales, HR, finance, and legal. Anywhere several people need to answer from the same address and see what everyone else has already said.
One person watching a busy address is a bottleneck waiting to happen, because traffic grows about 4% a year while the user base grows about 3%, so the load on each address keeps rising.
According to the Radicati Group’s Email Statistics Report, 2024-2028 counted 361.6 billion emails a day across 4.48 billion users in 2024. Its forecast puts 2026 at 392.5 billion a day and 2028 at 424.2 billion.
How does a shared inbox work day to day?
Five mechanics do the heavy lifting. Native shared mailboxes handle permissions and shared visibility. Assignment, collision alerts, and reporting usually come from shared inbox software layered on top.
| Mechanic | What it does | Why your team feels it |
| Message assignment | Puts one name against one conversation | Kills the “I thought you had it” problem |
| Collision avoidance | Flags when a colleague already has the thread open | Stops two people sending contradictory replies |
| Activity logs | Records who opened, replied, assigned, or deleted | Gives you an audit trail when something goes wrong |
| Permission management | Controls who can read, who can send, who can administer | Limits how much damage one compromised account can do |
| Real-time collaboration | Internal notes and shared drafts attached to the thread | Keeps context in the mailbox instead of scattered in chat |
How to add a shared inbox in Outlook
To add a shared mailbox to Outlook, you first need Full Access from your administrator. Once that’s granted, automapping usually adds the mailbox for you. Restart Outlook and check your folder pane before doing anything manual.
Adding a shared mailbox in Windows
New Outlook: Select Mail from the navigation pane. Right-click your account name in the Folder pane. Choose “Add shared folder or mailbox.” Type the address, for example info@contoso.com.
Classic Outlook: Open the File tab, select Account Settings > Account Settings, open the Email tab. Highlight your account and choose Change. Pick More Settings > Advanced > Add. Type the shared address, then confirm with OK, Next, Finish, and Close.
Outlook on the web: Right-click your name in the folder list and choose Add shared folder or mailbox.
Adding a shared mailbox for Mac
Open Tools > Accounts, select your own account, then open Delegation and Sharing. Under Open these additional mailboxes, click the + button and add the shared address.
Two things differ from Windows. Mac supports only Full Access, so other permission levels may not behave reliably. And there’s no automapping, so the mailbox never appears on its own.
How to access and send from a shared inbox
To reply from the shared address, choose New Email and pick it in the From field. If that field isn’t showing, turn it on with Options > From.
Permission levels decide what you can do:
- Full Access – read, file, and delete everything in the mailbox
- Send As – outgoing mail looks like it came from the shared address
- Send on Behalf – recipients see “Your Name on behalf of Shared Mailbox”
Grant the narrowest level that does the job. Full Access where Send As would do opens the entire message history to another person.
How to set up a shared mailbox in Google Workspace
A shared inbox in Google Workspace can be built three ways. Which one you pick depends on how much structure your team needs.
Native shared inbox
Google’s native shared inbox is the closest match to a Microsoft 365 shared mailbox. The administrator creates the mailbox and grants access. Delegates can then read, send, and delete messages, and view and add contacts.
- Sign in to the Google Admin console with an administrator account.
- From the Home page Users section, click “Set up a shared email address” and enter the address you want.
- Click Add new users and enter details for each person, or search by name to add existing users as delegates.
- Click Next. Skipping this step adds users to the account without giving them shared inbox access.
- Review the list of newly added users, click Next, then Done.
The feature is rolling out in phases, so check whether it has reached your console.
Collaborative Inbox in Google Groups
If the native option hasn’t landed, a Collaborative Inbox in Google Groups is the closest equivalent. Create a Google Group with the address you want, add members, then turn on Collaborative Inbox in the group’s settings.
Your team can then claim conversations, assign them, apply labels, and mark threads complete. Everything lives in the Groups interface rather than Gmail.
Two limits matter. Replies go out from each member’s personal address, not the group address. And there’s no collision detection or internal notes.
Important : Google’s Collaborative Inbox has no per-message privacy settings, so everyone in the group sees every conversation, even one assigned to a specific member. Plan your access list with that in mind.
Gmail delegation
The owner opens Settings > Accounts and Import > Grant access to your account, then adds colleagues by email address. Each delegate accepts an invitation and switches into the mailbox from their Gmail account switcher.
Google supports up to 1,000 delegates but recommends roughly 40 working at once. Delegation is desktop only.
Delegate a dedicated account, never someone’s personal inbox. Delegates see everything in the mailbox they’re added to.
What can go wrong with a shared mailbox?
Permissions get configured once and then forgotten. That’s where the trouble starts.
Shared passwords and broken MFA
Handing one login to five people is the most common shortcut and the worst one. A shared mailbox should not be used through direct sign-in.
Two-factor authentication can’t do its job on a credential a whole team types in. You also lose any record of who did what.
Stale access
People change roles. Contractors finish. Interns leave. Review access lists regularly, or old permissions pile up silently.
One compromise reaches everyone
One phishing email that catches one team member hands the attacker the whole inbox, archives included. From there, a compromised address becomes a convincing platform for phishing colleagues and customers.
Your provider can read everything
Native shared mailboxes on Microsoft 365 and Google Workspace are encrypted at rest, but the provider holds the keys. No amount of permission tuning removes that. End-to-end encryption does.
Do you need shared inbox software?
Native mailboxes handle access. They don’t handle workflow. Shared inbox software layers assignment, internal notes, collision detection, and response-time reporting over an existing Gmail or Microsoft 365 account.
It’s worth the cost once more than ten people touch the queue and you’re measured on response time. Below that, written ownership rules do the same job for free.
One trade-off is easy to miss: shared inbox software usually processes mailbox content to power assignment, notes, and reporting, so you’re adding a third party to the list of companies handling your team’s correspondence. If privacy is the priority, Mailfence is a different model: mailbox sharing happens inside Mailfence Groups, and messages encrypted with OpenPGP are unreadable to Mailfence itself.
Which providers keep messages private?
| Provider | Shared mailbox? | How access works | Can the provider read content? |
| Microsoft 365 / Exchange | Yes | Admin grants Full Access or Send As | Yes |
| Google Workspace | Yes | Admin assigns delegates via Gmail delegation or Google Groups Collaborative Inbox | Yes |
| Tuta | Yes | Admin creates a shared mailbox and adds members | No |
| Mailfence | Yes | Owner shares mailbox with members of the same Mailfence Group | No |
| Proton Mail | Groups only | Group addresses forward mail to all members | No, for personal mailboxes |
| Shared inbox software | Yes | Adds assignment, notes and reporting on top of Gmail or Microsoft 365 | Yes |
Two questions settle it. Can anyone outside your team read these messages? And can you cut one person’s access without disturbing everyone else’s?
Mailfence — Your secure Productivity Suite
Reclaim your Privacy with
- Messages
- Calendars
- Documents
- Groups
How Mailfence shared mailboxes work
Mailfence builds mailbox sharing on top of Mailfence Groups, so access follows people rather than passwords.
Prerequisites
- The mailbox owner and accessor(s) accounts need to be member of the same Group.
- The user that wants to give access to his/her mailbox, needs to have a Pro or Ultra subscription plan that allows this function.
Note: free account can also send emails using any of the shared mailbox addresses, you do not need a paying subscription. Users can also create one dedicate signature for each mailbox they have access to.
How to activate mailbox sharing
Click your profile portrait at the top right, then Settings. Choose Messages > Mailbox sharing in the left column. Click add a user, pick members from a Group you administer or belong to, select the group workspace from the dropdown, and confirm with OK.
To revoke access later, select the member and click the X icon. Full instructions can be found in How to set up a shared mailbox.
What access covers
Colleagues reach the mailbox from the pull-down menu under the logo at the top left, the same one used for group environments. Access is total: every folder is available, including Inbox, Sent, Trash, and Templates.
Mailfence has no Send As or Send on Behalf distinction, so anyone with access sends as the address itself. Because access is per person, everyone keeps their own login and two-factor authentication.
How to fix a messy shared inbox
A fragmented inbox is an inbox that has been split into pieces without anyone noticing. Instead of one clean place where messages arrive and move through a simple workflow, the work gets scattered across multiple copies, multiple forwards, multiple folders, and multiple versions of the same conversation.
- Stop forwarding emails. Keep everything in one place.
- Decide who answers. Make one clear rule.
- Use three folders. Waiting on customer, waiting on us, done.
- Set reply times. Everyone follows the same timing.
- Split the inbox if it’s too busy. One address per topic.
- Check access regularly. Remove old accounts and reduce permissions.
How to choose the right shared mailbox?
Pick based on team size, message volume, workflow needs, and whether you want a native mailbox or a dedicated shared inbox platform.
| Team / use case | Best choice |
| 2–5 people, low volume | Microsoft 365 shared mailbox, Google Workspace collaborative inbox, or a simple delegated mailbox |
| 5–20 people, steady volume | Native shared mailbox plus clear ownership rules; add shared inbox software if you need assignment tracking or reporting |
| 20+ people, high volume, service targets | Dedicated shared inbox software or a full helpdesk |
| Any size, sensitive information | Mailfence or Tuta if privacy is the priority; Microsoft 365 or Google Workspace if you want a broader workplace ecosystem and the most mature shared-mailbox workflows |
If you already work in Microsoft or Google, their native options are the easiest fit. If privacy is the priority, choose Mailfence or Tuta. If you want a broader workplace ecosystem and the most mature shared-mailbox workflows, choose Microsoft 365 or Google Workspace. And if privacy becomes a higher priority later, you can switch from Google or Microsoft to Mailfence.
Final thoughts
Most teams notice the difference within a week. Duplicate replies stop. Gaps in coverage become visible instead of just being felt. And the address stops belonging to whoever happens to be answering it this month.
The part teams skip is the security layer underneath. Per-person logins with 2FA, narrow permissions, and a quarterly access review cost almost nothing and close the gaps that cause real incidents. Encryption closes the last one, the one permissions can’t touch.
Privacy and security aren’t a trade-off at all: “Security guarantees privacy, and privacy guarantees security.” – Patrick De Schutter, Co-Founder of Mailfence
If you’d rather your team’s inbox stayed unreadable to everyone outside it, Mailfence offers mailbox sharing inside a full productivity suite: encrypted email, calendar, documents, contacts, and groups, hosted in Belgium under GDPR.
Mailfence – a secure and private email service. Follow us on twitter/reddit and keep yourself posted at all times.
Get the latest privacy news in your inbox
Sign up to the Mailfence Newsletter.
FAQ about shared mailboxes
How do I prevent accidental data exposure?
Limit who can access the mailbox, review permissions quarterly, and avoid forwarding sensitive threads into personal inboxes. If the content is confidential, use end-to-end encryption so only your team and the intended recipients can read it.
How does a shared mailbox fit into GDPR?
GDPR requires clear access control, auditability, and minimisation. A shared mailbox helps by centralising messages instead of scattering copies across personal accounts. For sensitive data, choose a provider like Mailfence offering end-to-end encryption so the content stays unreadable to anyone outside your team.
Should I use shared inbox software or stay with a native shared mailbox?
Use native mailboxes when the team is small and volume is manageable. Move to shared inbox software when you need structured workflow: assignment, internal notes, collision detection, SLAs, or analytics.
Do you need a license for a shared mailbox in Microsoft 365?
Not usually. Each user needs their own licensed Exchange Online mailbox, but the shared mailbox itself does not require one. Three exceptions apply: unlicensed mailboxes cap at 50 GB, 100 GB or litigation hold requires Exchange Online Plan 2, and enabling direct sign-in triggers a license requirement.
How does a shared inbox work in Google Workspace?
Three ways: a native shared inbox, a Collaborative Inbox in Google Groups, or Gmail delegation. The native shared inbox is closest to a Microsoft 365 shared mailbox, Collaborative Inbox runs through Google Groups, and delegation grants access to a single account.
How is a shared inbox different from a distribution list?
A distribution list copies each message to every member’s inbox. A shared inbox keeps one copy in one place so everyone sees the same thread, replies, and sent items.
Can a shared mailbox be encrypted?
Yes, though what “encrypted” means varies by provider. Microsoft 365 and Google Workspace encrypt mailbox data at rest and in transit, but they hold the keys and can decrypt the contents. End-to-end encryption is the different guarantee: only sender and recipient hold the keys.
