<!--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=334310) </details> <!--IssueSummary end--> ### Problem to solve When creating or editing the setting for a protected branch and choosing options for `Allowed to merge` and `Allowed to push` the role/group/user selection dropdown allows a user to select `No one` and will also allow the selection of additional groups/users. This creates a confusing situation where a user needs to interpret what rule will be enforced. Is it no one, or the selected users? Our UI should be explicit and clear about what impact selections will have.  ### Proposed solution Do not allow additional selections of additional users/groups if `No one` is selected. ### Important consideration We need to account for the impact this change may have on users that have chosen this configuration and determine a way to role out the change without negative impacts.