I have set security up so that there are 2 groups: Administrators, with unlimited rights, and Maintainers, whose rights are more limited. I have some pages which are in effect holders for subpages where the real content is (the end user first selects the parent page then the child page from a nested menu). I want Maintainers to be able to edit the content of the subpages but NOT be able to edit the parent (holder) pages (which are in effect part of the design of the website).
So, I set "Who can edit this page?" for the parent to just the Administrators group, then for the children, I check both the Administrators and Maintainers boxes, saving as I go along. But evidently Silverstripe does not like what I'm doing because it doesn't save the permissions (although no error comes up). When I move away from the parent page and then come back to it, the 'Only these people (choose from list)' radio button is still set for 'Who can edit this page?', but with no groups - it has forgotten them. This is the same with 2.3.3 and 2.3.4.
Am I misunderstanding something about the security in Silverstripe? Is it not possible for subpages to have more liberal editing permissions than their parent page?