Separate Administration Panel from User Configuration

Problem //////////////////////////////////////////

Currently, administrative functions (billing, user management, domains, policies) and personal user settings (mail preferences, calendar settings, app configurations) are mixed within the same interface. This creates confusion, increases the risk of accidental changes, and blurs the line between organizational control and individual customization.

Proposal //////////////////////////////////////////

Create a clear separation between:

• Admin Panel for organization-wide settings (billing, users, domains, security policies)
• User Settings for personal preferences (signatures, themes, notifications, app behavior)

This separation should apply both in the UI and in the underlying permission model.

Why it matters //////////////////////////////////////////

Admins can focus on organizational tasks without navigating through user-level options. Users get a cleaner interface without seeing settings they cannot change anyway. It also improves security by reducing the attack surface when a regular user account is compromised.

Related //////////////////////////////////////////

This aligns with the existing request for admin accounts that do not consume a user seat:

Admin Account Without Consuming a User Seat:
https://protonmail.uservoice.com/forums/945460-general-ideas/suggestions/50820329-admin-account-without-consuming-a-user-seat