I will never enable the Add or remove “XYZ” role members" permission ever. There is an inherent danger in enabling this permission because it allows members of a collaboration role to strip equally roled members of the permissions assigned to the role or grant them to an unwanted outsider. However, if I were to leave this off, that means I as the group owner need to always have a hand in assigning roles and can’t delegate this to lower-ranked members like I can with legacy roles - for example, I would want developers to be able to grant play permissions, but absolutely not grant others edit access; and I wouldn’t want other testers removing the role from each other or from developers.
I don’t personally see the merit in allowing members of a role to control the assignment of it to people of equal standing, it just seems like an inherent flaw especially when the direction of Roblox is to further empower these roles with permissions with the group, Studio access and even access to group funds. It’s incredibly dangerous to lack hierarchical control, or even moreso specifying a list of roles that another role can add or remove users from. It needs to change so if the owner desires, there’s less reliance on them to assign basic permissions without the legacy roles system which is already lacking (e.g. I can’t blanket grant a legacy role the ability to play all or some experiences).