<!--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=554103) </details> <!--IssueSummary end--> <!--This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Problem Statement A [large Ultimate, Self-Managed customer](https://gitlab.lightning.force.com/lightning/r/Account/0016100001NKU63AAH/view) ran into the situation where the instance-level setting "Prevent editing approval rules in projects and merge requests" was enabled, and the "Add approval rule" button completely disappears from Project Settings → Merge requests without any explanation. This creates a poor user experience where Maintainers expect to be able to configure approval rules but cannot find the functionality. ### Current Behavior * User navigates to Project Settings → Merge requests → Merge request approvals section * "Add approval rule" button is completely missing from the "Approval rules" section * No indication of why it's unavailable  ### **Proposed Behavior** When the admin setting "Prevent editing approval rules in projects and merge requests" is enabled, instead of hiding the "Add approval rule" button completely, GitLab should behave the following way: 1. User navigates to Project Settings → Merge requests → Merge request approvals section 2. Show the "Add approval rule" button in a disabled state (grayed out, non-clickable) 3. Provide a clear explanatory tooltip on hover that explains why this option is not available for the user: * In this situation, a statement like this could be displayed: "Approval rule editing has been disabled by your GitLab administrator. Contact your admin to modify the 'Prevent editing approval rules' setting in Admin Area." * Another statement could be displayed if the user doesn't have sufficient role permissions. <!--Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.--> <!--Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/-->