Restrict Project Creation under Groups

Summary

Customer would like to be able to restrict users, including Master and Owner roles, from creating projects beneath groups. This would mean that only Admin users can create projects for any group. The reason for this is so that the admins can ensure that naming conventions are adhered to and project permissions are correct for each project created. Master and Owner user should maintain all other privileges aligned with their role.

This would not prevent users from creating their own Personal projects.

Project creation could be restricted across the board by setting the project limit to zero for each individual user, but this would prevent the creation of personal projects.

Relevant Zendesk Ticket

• https://gitlab.zendesk.com/agent/tickets/31647

@JobV - What do you think?

@markglenfletcher hm, problematic. Especially for Owners and Masters, as it conflicts with their further permissions (ability to destroy projects, rename them, etc).

Is it not acceptable for them to make the users Developers in the group? That way this would be achieved, barring the only issue adding new users to the group.

Agreed. We shouldn't make a special case for this. It's sort of related to 'Restrict group owners to admins' that we talked about another issue. Beyond that, we should only implement this as part of an enhancement to roles/permissions (custom).

added ~480950 ~1208338 labels

Hi,

First of all, thank you for raising an issue to help improve the GitLab product. This issue was labelled as a ~"feature proposal" in the past. In order to maintain order in the issue tracker, we are starting to close off old, unpopular feature proposals that have not gained many votes since opening.

This issue will be marked for closure, as it meets the following criteria:

• Created over 1 year ago
• Labelled as a ~"feature proposal"
• Unscheduled (not associated with a milestone)
• Less than 10 upvotes

Thanks for your help and please raise any new feature proposals as a new issue.

/cc @markglenfletcher

We are reverting the above policy regarding old, feature proposals until we find a better solution. Sorry for the noise.

The issue will no longer be marked for closure.

added Manage [DEPRECATED] label

added devopsmanage label

added [deprecated] Accepting merge requests label

added groupauthentication and authorization [DEPRECATED] label

removed [deprecated] Accepting merge requests label

Customer ticket: https://gitlab.zendesk.com/agent/tickets/141606 (internal use)

Setting ~"Category:Authentication and Authorization" based on ~"group::access".

Setting ~"Category:Authentication and Authorization" based on ~"group::access".

added 1 deleted label

changed the description

added sectiondev label

We have an ultimate customer that also needs this feature.

ZD(internal) - 196492

added Category:System Access label

added devopsgovern sectionsec labels and removed devopsmanage sectiondev labels

added to epic &9973

changed milestone to %Backlog

We have something that solves this with supported SAML attributes - projects_limit - https://docs.gitlab.com/ee/user/group/saml_sso/#supported-user-attributes

added groupauthentication label and removed groupauthentication and authorization [DEPRECATED] label

added groupauthorization label and removed groupauthentication label

removed Manage [DEPRECATED] label

added workflowproblem validation label

removed workflowproblem validation label

Setting label(s) Category:Permissions based on groupauthorization.

Setting label(s) Category:Permissions based on groupauthorization.

added Category:Permissions label

mentioned in issue #435333

marked this issue as related to #241797 (closed)

marked this issue as related to #118873

marked this issue as related to #378345 (closed)

marked this issue as related to #18647 (closed)

Is a duplicate of #241797 (closed)