Draft: Resolve "Add new static role Security Manager"
What does this MR do and why?
This change introduces a new "Security Manager" role with an access level of 35, positioned between Developer (level 30) and Maintainer (level 40) in the permission hierarchy. The Security Manager role is designed for team members who need to manage security settings and track security issues. The implementation includes:
- Adding new constants and string representations for the Security Manager role
- Adding helper methods to assign users to this role
- Creating policy conditions to check for Security Manager access
- Adding the role to GraphQL queries and responses
- Updating factories and tests to support the new role
The change is comprehensive, affecting JavaScript constants, Ruby models, policies, GraphQL schemas, and test files to thoroughly integrate the new role into the system.
References
Related to #524829
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Edited by Miki Amos