Enable organizations to manage personal spaces of group managed accounts
Problem statement
When an organization uses a self-hosted instance of GitLab, they maintain full control over the security of all projects and their users. For example, if a user sets up an undesirable project in their personal space (or one with too lax of security settings), they have the tools to address the problem directly.
With GitLab.com, they currently do not have these access rights. If one of their users accidentally creates a project with too broad of access, their only recourse currently is a DMCA take down request which can be burdensome and slow.
Proposed solution
For group managed accounts (&709 (closed)), we should allow the organizational entity the ability to manage these user accounts and the content they create.
In the example above, they should have the access rights to view the personal projects of these users, and modify the access settings or remove projects. This would be analogous to the level of control they would enjoy on a self-managed instance, but only for dedicated corporate user accounts which go through their SSO system.