Prevent deleting a namespace on GitLab.com if it's attached to an active subscription
Problem to solve
As a user with Owner permissions in a top-level namespace on GitLab.com, I want to mitigate the risk of an accidental or malicious deletion of my organization's namespace.
I believe it to be nearly universally true that given the presence of an active paid subscription, deletion of the namespace it's tied to is unwanted. Even renaming of the namespace is something that should likely demand the involvement of GitLab support (i.e. a GitLab Team Member with admin privileges).
For various reasons, it may be necessary for a number of members of the namespace to hold Owner permissions, for example, managing group-level CI/CD variables requires the Owner role. Limiting the attack vectors available to Owners is important for organizational security posture.
Intended users
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
User experience goal
A user or organization desiring a move or deletion of their namespace for the duration of an active subscription would be required to reach out to GitLab Support with a request to execute this. Support would undertake sufficient identity validation before honouring the request.