<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=4007) </details> <!--IssueSummary end--> ### Description When using Gitlab in an enterprise environment with may developers there is a need to restrict who can approve merge requests as well as minimizing administration of Gitlab it self. A solution to this would be to allow LDAP groups to be used as merge request approvers. This will have the benefit of a one time configuration of the gitlab project(s) and any further administration is done in LDAP where users can be added/removed from the merge requests approvers role. #### Use cases Users with many projects and many developers that need ease of use and low administration overhead. ### Feature checklist Make sure these are completed before closing the issue, with a link to the relevant commit. - [ ] [Feature assurance](https://about.gitlab.com/handbook/product/#feature-assurance) - [ ] Documentation - [ ] Added to [features.yml](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/features.yml)