<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary 客户通过gitlab管理界面 `admin`-`设置`-`可见性与访问控制`-`允许删除项目`-`管理员` 设置成只有管理员可以删除项目后，但是如果给某个群组分配了`onwer`权限后，那么这个onwer权限的权限虽然不能直接删除该群组下的项目，但是却可以直接删除这个群组，这样间接就拥有了删除项目的权限。 <!-- Summarize the bug encountered concisely. --> ### Steps to reproduce 验证需要专业版以上的license - 客户版本： gitlab-jh-15.5.4 - 自测版本： gitlab-jh-15.5.4 gitlab-jh-16.2.3 gitlab-jh-16.4.1 ## 设置`管理员` 允许删除项目  ## 分配群组owner权限 群组权限  继承群组权限  ## 通过owner权限的用户登录，发现可以删除此群组（但是如果直接删除群组下的项目的话，是没有权限删除的）  <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? <!-- Describe what actually happens. --> ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> ### Relevant logs and/or screenshots <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> ### Output of checks <!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->