Docs bug: "Protected Branches" Docs Does Not Sufficiently Cover The Ability to Use Custom Groups

Problem to solve

In regard to this Protected Branches documentation page: https://docs.gitlab.com/ee/user/project/protected_branches.html

In the actual product it is extremely hard to discover that Custom Groups (Not Roles) can be used in branch protections because the entire "Group" section of the drop down does not appear unless at least one custom Gitlab group has been added to the Repository under "Members".

Since advanced enterprise implementations may weigh heavily on this part of GitLab's Role Based Access Control (RBAC), it is important that it is easy to discovery both during product assessment and after adoption.

Individuals responsible for assessing the flexibility of GitLab change controls while in a pre-sales mode can easily miss this critical flexibility.

Generally such reviewers will use exploration of the UI and documentation to understand the full flexibility of the product.

If the reviewer does not have access to the appropriate product level - they may not be able to configure the feature anyway - in which case documentation is all they have to go by.

This challenge is compounded by the fact the documentation does not sufficiently discuss nor screenshot the ability to use custom groups in Protected Branches (issue opened here: #37342 (closed))

Proposal

This documentation page should show this feature in screenshots and mention that groups do not appear in the drop down selector unless they have first been added to the project in the project's "Members" page. The new "Group" documentation should be tagged with the required GitLab edition.

Docs bug: "Protected Branches" Docs Does Not Sufficiently Cover The Ability to Use Custom Groups

Problem to solve

Proposal

Who can address the issue

Other links/references