Current Limitation: Currently, Proton Mail does not allow a single custom email address (alias) to be assigned to multiple user accounts within a Family or Duo plan. When an administrator creates an alias (e.g., info@myfamily.com or support@mybusiness.com), it can only be assigned to one specific user.

This forces users into inefficient workarounds:

Manual Forwarding: One person owns the alias and must set up filters to forward mail to others. This breaks the "shared inbox" experience, as replies come from the individual's address, not the group address, and there is no central view of the conversation history.
No Collaboration: Multiple team members cannot log in to the same mailbox to manage tickets, customer inquiries, or family correspondence simultaneously.
The Request: I am requesting the addition of a Native Group Alias or Shared Inbox feature for Proton Family and Proton for Business plans.

Desired Functionality:

Multi-User Assignment: Allow an administrator to create an alias (e.g., team@domain.com) and assign it to multiple user accounts simultaneously.
Shared Inbox View: When any assigned user logs in, they should see emails sent to this alias in a dedicated folder or shared view, alongside their personal mail.
Unified Sending: Allow any assigned user to "Send As" the group alias, ensuring replies come from the group address (e.g., team@domain.com) rather than the individual's personal address.
Conversation Sync: Ensure that if User A replies to a thread, User B sees that reply in the shared view, maintaining a single conversation history.
Why This Matters: This is a critical feature for:

Small Businesses: Teams need to manage support@, sales@, or info@ addresses without relying on a single "owner" account.
Families: Families managing a shared household email (e.g., vacation@, school@) need all members to see and respond to messages without forwarding chains.
Competitiveness: Competitors like Google Workspace and Microsoft 365 offer "Shared Mailboxes" and "Distribution Groups" as standard features. The lack of this capability is a significant barrier for small businesses considering migrating to Proton.
Conclusion: While the current workaround of manual forwarding exists, it is clunky and lacks the collaborative features necessary for professional or shared household use. Adding native support for group aliases would significantly enhance Proton's utility for teams and families.

Thank you for considering this request.