Allow read-only access to escalation policies for auditors
What does this MR do and why?
See https://docs.gitlab.com/ee/administration/auditor_users.html
Users with auditor access have read-only access to all groups, projects, and other resources except:
Screenshots or screen recordings
- Login as an Auditor
- Visit http://localhost:3000/gitlab-org/gitlab-test/-/escalation_policies
| Before | After without policies | After with policies |
|---|---|---|
 |
 |
 |
Read-only
Although we are showing "Create", "Edit" and "Delete" buttons the actions are read-only and auditors see an error message.
| Creating | Editing | Deleting |
|---|---|---|
 |
 |
 |
In a follow-up #374149, we need to hide these buttons when when administration is not possible. This is also true for "On call schedules".
How to set up and validate locally
- Create an auditor
- Impersonate as an auditor
- Visit http://localhost:3000/gitlab-org/gitlab-test
- See Monitor > Escalation Policies item in the navigation bar
- Visit http://localhost:3000/gitlab-org/gitlab-test/-/escalation_policies
- See screenshots above
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #358633 (closed)
Edited by Peter Leitzen