Documentation - Cascading settings
In #321724 (closed) and #324097 (closed) we are introducing a concept of "Cascading settings". This means that a group setting can be enforced at the application/instance level or the group/namespace level. As a MVC this will only apply to the Enable delayed project removal setting and will only be enforceable at the group/namespace level. But the goal is to make this consistent across all settings.
Possible ideas for documenting:
1️⃣ Add a new "Cascading settings" page to https://docs.gitlab.com/ee/user/group/
Add a new "Cascading settings" page to https://docs.gitlab.com/ee/user/group/ that explains what a cascading setting is and which settings can be enforced at the group/namespace level and which settings can be enforced at the application/instance level. Maybe have a table with checkboxes. Right now it would just look something like this:
Setting | Enforceable by group setting | Enforceable by admin area setting (FREE SELF) |
---|---|---|
Enable delayed project removal | ✓ |
2️⃣ Add a "Cascading settings" section in "Admin Area settings"
Add a "Cascading settings" section in "Admin Area settings" that explains which settings can be enforced at the application/instance level. This probably doesn't make sense for the MVC because the Enable delayed project removal
setting can't yet be enforced at the application level.