### Summary - When a group is not protected, new sub-folders are protected, they should inherit the setting from it's parent. - When you change the parent group to be unprotected, the existing children are not affected. ### Steps to reproduce - Create a group with some sub-groups / folders - Change the main group to be unprotected by default - None of the childs are affected - Even if you create a new sub-folder it will be protected as well ### What is the expected *correct* behavior? - These changes should be inheritable and affect all the child nodes, much like the 2FA protection ### Output of checks This bug happens on GitLab.com