### Problem to solve Allow the ability to manage a set of MR approvers at a GitLab group level instead of per project. All projects within the group would utilize the approvers defined at the group level with the ability to override (at the project level) if a different approver should be defined. ### Target audience - Delaney, Development Team Lead, https://design.gitlab.com/research/personas#persona-delaney - Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon - Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney - Sam, Security Analyst, https://design.gitlab.com/research/personas#persona-sam <!--- For whom are we doing this? Include a [persona](https://design.gitlab.com/research/personas) listed below, if applicable, along with its [label](https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A), or define a specific company role, e.g. "Release Manager". Existing personas are: (copy relevant personas out of this comment, and delete any persona that does not apply) - Parker, Product Manager, https://design.gitlab.com/research/personas#persona-parker --> ### Further details <!--- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal <!--- How are we going to solve the problem? Try to include the user journey! --> ### What does success look like, and how can we measure that? Similar to being able to set-up a project level approver default, you would set that at the group level. Project can override group and an individual MR can override either project or group. The current method of creating the approval at the project level can be re-used for group. <!--- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this --> ### What is the type of buyer? (Which leads to: in which enterprise tier should this feature go see https://about.gitlab.com/handbook/product/pricing/#four-tiers ) I think this could initially be limited to Premium or above -- or even Ultimate. ### Links / references