approval settings at group or sub-group level

Problem to solve

Organisations might need to be able to define approval settings on a group or sub-group level, as certain people/teams may be granted rights on a different level than projects. Also with regards to automation, configuring these approval settings (which could be because of corporate policy) could follow the same structure as it would for RBAC. Including the exclusion of, or deviating from, these settings by using automation.

Target audience

Organisations that have (more) fine-grained needs for configuring approvals. Anyone that wishes to have more flexibility on approval settings rather than just on the project level.

Further details

Approval settings on Group or sub-group level to enforce settings from above, and have projects inherit the configuration.

Proposal

Same concept as for user permissions. configure on a higher level, inherit to everything underneath. With option to enforce, without being able to change on any lower level.

What does success look like, and how can we measure that?

Difficult to measure from a GitLab pov I guess

What is the type of buyer?

Enterprise edition, because that's where approvals enter in the first place.