Shared Mailboxes & Team Inboxes: The Missing Link for M365 Business Migrations
Hello Proton Team,
We are currently migrating our business from Microsoft 365 to Proton. The single largest operational gap in our day-to-day workflow is the lack of native shared mailboxes for generic team addresses such as office@, invoices@, or support@. For many European SMEs, this missing functionality is the primary blocker that prevents them from switching or causes them to abandon the migration.
The Practical Problem:
In almost every business, central mailboxes must be accessed and monitored by multiple employees simultaneously—often with different permission levels (e.g., read-only access for field technicians/installers, full processing and sending rights for back-office staff).
The current workarounds are unviable for businesses:
Sharing credentials for dedicated user accounts: This directly violates fundamental security and compliance standards, complicates multi-factor authentication (MFA), and prevents reliable audit logs. Furthermore, it forces companies to pay for a full business seat for every single functional address, even if it only serves as an operational queue.
Simple forwarding rules: Forwarding does not solve the issue because workflow states ("Who is working on what?", labels, read/unread states) are not synchronized, inevitably leading to duplicate effort and miscommunication.
Why This Is Crucial for Proton’s B2B Growth:
With shared vaults in Proton Pass and shared folders in Proton Drive, you have already proven that zero-knowledge encryption and multi-user access work seamlessly together. Implementing that same cryptographic model for mailboxes would be the decisive catalyst to help companies break free from Microsoft Exchange and Google Workspace.
Core Requirements:
Direct access to functional team mailboxes within each user's primary Proton interface (web, desktop, mobile) without the need to switch user profiles.
Granular, role-based access permissions (e.g., view/read-only vs. send-as / reply permissions).
Synchronized real-time status (shared labels, tags, and read status across all authorized users).
Delivering native shared mailboxes would resolve one of the most significant operational hurdles in the B2B sector and firmly establish Proton as a complete, privacy-first enterprise solution.