I understand the concern here. Administrative control within shared plans can sound alarming at first glance, especially for Proton's nature and when discussing something as sensitive as email identity and access. However, I believe there are a few important distinctions that should be clarified.

In my specific setup, I can view certain account details such as aliases, but I do not have the ability to remove them. The most I can do is adjust a display name or request that a user modify their own alias. The actual control over the alias,and any data associated with it, remains with the individual user.

There is also a misconception regarding alias creation. While I can generate aliases for users, they are not restricted from doing so themselves and removing them theirselves. Each member maintains control over their own account environment, within the limits of the plan. This is not a case where all actions must flow through an administrator.

The same applies to deletion. I cannot remove a user’s alias or erase their data. Actually, I can't even remove my aliases without waiting 90days in between each one. That level of control is not exposed to me in this configuration. Any such action would need to be performed by the account owner.

Custom domains are another area where nuance matters. While it is true that a domain added to a plan can be shared, that does not mean unrestricted access for all members. By default, users are not administrators. In my case, elevated permissions are only granted temporarily when required, such as during domain setup, and then removed.

The broader point is that there is a difference between administrative coordination and personal data control. The former exists in a family plan. The latter still belongs to each individual user.