<!--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> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=577324) </details> <!--IssueSummary end--> # Context See https://gitlab.com/gitlab-org/gitlab/-/merge_requests/208771#note_2823214240 In https://gitlab.com/gitlab-org/gitlab/-/issues/569901 https://gitlab.com/gitlab-org/gitlab/-/merge_requests/208771, users are prevented from editing a group-level branch rule on the project level to reduce confusion. Users can still manually edit their url to navigate to a group-level branch rule page in the project-level branch rule section. Ex: `http://gdk.test:8080/flightjs/Flight/-/settings/repository/branch_rules?branch=\*-group-level` When users manually navigate to a group-level branch rule page inside the project-level branch rule section, display an empty state. # Design proposal <table> <tr> <th> Current state from https://gitlab.com/gitlab-org/gitlab/-/merge_requests/208771 </th> <th>Proposed</th> </tr> <tr> <td> {width="1223" height="693"} </td> <td> User **DOES** have permission to view group-level Protected Branches  User **DOES NOT** have permission to view group-level Protected Branches  Illustration: https://gitlab.com/gitlab-org/gitlab-svgs/blob/main/illustrations/empty-state/empty-groups-md.svg </td> </tr> </table>