Child page does not inherit page restrictions from parent page
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
A child page is supposed to inherit the page restrictions from its parent page, but, for some reason, it does not inherit any restrictions.
Diagnosis
Double confirm that the parent page has restrictions applied. Else, create a new page, add some restrictions to the page and create a new child page under it. The child page will inherit those restrictions by default. This will be depicted by an open red padlock icon. Note: Only view restrictions are inherited, Edit permissions are not inherited. See CONFSERVER-5095 - Getting issue details... STATUS
Cause
The ancestor table will become out of sync occasionally.
Resolution
Access this URL:
http://yoursite/admin/permissions/pagepermsadmin.action
After rebuilding the ancestor table, you need to flush the "Inherited Content Permissions" cache in Cache Statistics, otherwise, the inherited permissions may not be applied immediately to all pages. You may also need to rebuild the content index so that the restriction will take effect.
Screenshot: Page level permissions
