## Problem to solve It is possible to set push rules at a project level, and an instance level, but it isn't possible at the group level. As a GitLab.com subscriber, I have no way to enforce push rules across my organization. As a group maintainer on a self-hosted instance, I have no way to enforce push rules across my team. This is important because groups may be hundreds of people and hundreds of projects. I want the owners of the individual projects to have as much flexibility as possible, but need to enforce certain requirements. ## Further details This is a capability gap in a feature that already exists. The group-level implementation should apply the tiering outlined in [our docs](https://docs.gitlab.com/ee/push_rules/push_rules.html#enabling-push-rules) for the respective push rules. ## Proposal Add a new **Push rules** settings page to **Groups** that has the same capabilities as the **Instance** settings page. - group **Maintainers** will be able to set these rules if not already set by an administrator - project **Maintainers** will not be able to override Instance or Group push rule settings  ## Links / references