## Problem When a user creates a project in group in which he has master privileges he does not get owner privileges for the new project. Is that intentional? That implies that projects created in the group can only be deleted by group owners but not by the user who created the project originally. ## Proposal We follow a similar pattern as for subgroups. We want to be as consistent as possible between groups and projects moving forward. * This behaviour is controlled as it is for subgroups. [This setting](https://docs.gitlab.com/ee/user/admin_area/settings/visibility_and_access_controls.html#define-which-roles-can-create-projects) defines whether or not a developer should be able to create projects in the first place. * `DEVELOPERS` who are allowed to create projects become `OWNER` of the project upon creation. An explicit membership record is created. * If the `DEVELOPER` is downgraded in the ancestor groups, they remain `OWNER` of the project. * If the `DEVELOPER` is removed from the ancestor groups, the option `Also remove direct user membership from subgroups and projects` will have to be explicitly checked to remove the `OWNER` from the project as well Due to security, financial and operational concerns, we will look into https://gitlab.com/gitlab-org/gitlab/-/issues/381452+ before taking up work on this issue.