WIP: Add guidlenes for inheritance and enforcement to settings
What does this do?
Adds a section to the settings page to define a standard inheritance and enforcement model. This is useful because it establishes a repeatable pattern for scaling various settings.
Problem to solve
Having restrictive settings at the project level are useful for setting boundaries. However, only having them at the project level can make administration a pain if there are thousands of projects. As such, a number of customers have requested for settings to cascade down from a higher level with an escape hatch when necessary.
Lack of definition can lead to unintended consequences → Group push permissions can enforce project-level insecure settings
Related Issues
Instance Level
Group/Subgroup
Edited by Austin Regnery