Inherited Page Restrictions Are Not Respected
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Symptoms
Please note that edit restrictions are not inherited, by design. See Page restrictions for more information.
Assuming the following setup:
1
2
|-Parent Page A (restricted to user:jsmith only)
|-Child Page 1
The child page should also be restricted to jsmith only. However, child page 1 is visible to the all people who have the appropriate space perms.
Cause
This was a known bug during upgrade of Confluence 2.9.x - CONFSERVER-12911 - Pages that inherit page restrictions are not respecting those restrictions after upgrade to Confluence 2.9. It is resolved in 2.10.x. However, the ancestor tables that handle the parent child relationships do not get updated properly, and the problem may persist. This is being tracked at CONFSERVER-25189 - Confluence Page View Restriction is not Inherited when Ancestor CONFANCESTORS Table Gets out of Sync
Resolution
Visit this URL as an admin:
1http://<confluence address>/admin/permissions/pagepermsadmin.actionClick the button rebuild the ancestor relationships for the Confluence content. Depending on the size of your Confluence instance, this task could take 10 minutes or more to complete.
Flush the Inherited Content Permissons cache so that the rebuilt permissions are picked up. See Cache Statistics.
Was this helpful?