Remove maintainer access to administer compliance frameworks
What does this MR do?
- backend - Restricts the ability for project maintainers to assign a compliance framework to a project.
- frontend - Alters frontend to match new ability. (Only read-only)
-
documentation changes:
- Updates permissions matrix
- Changes some of the badges to make it clear that this is a SaaS and self-managed feature.
Screenshots (strongly suggested)
Owner View | Maintainer View |
---|---|
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec
-
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Related to #299861 (closed)
Edited by Max Woolf