Many organizations require all changes to be reviewed and approved by specific groups of people before a change can be merged (e.g. every change must be approved by at least: 1 staff engineer, 1 product manager, 1 production engineer). GitLab only supports selecting users (and groups) who can approve the change and a minimum number of approvals required. In this structure it is impossible to enforce the sign off structure in the example above. ### Use cases **Best practices** – GitLab uses merge request templates to remind people to seek review from backend, frontend, database, and UX before a change is merged. These are not enforced. They are meant to be followed but we trust our team and their judgement to skip these when these reviews are not required. Rather than using a checklist, a non-enforcing mode could help increase visibility and automatically check the change off. **Enforcing workflows** – other organizations require very specific people to approve every change, typically as part of an internal process designed to demonstrate a policy that meets some external requirements. For example, a financial institute might develop internal policies that require every merge request to be approved by a business sponsor and QA lead. ### Vision GitLab allow organizations to specify with detail which people should/must approve a merge request. ### Proposal TBD