Cannot view children of parent pages ("This section is managed by the Project Manager")
Asked by Jack Vandemeulebroecke:

Hello,

I have a space with a Child Display Macro in the overview. With all the required permissions and restrictions set, users (who *aren't* the ones that created said restrictions) cannot see the children in the Children Display Macro from the overview. Additionally when they go to the parent page they cannot see the children in it despite having the required permissions to view (and even edit) them.

I am positive that the users that need to view the Child Display Macro are in the correct groups that have the proper restrictions set to view the children. I have included screenshots of what the person who made the restrictions sees (the correct view) and what everyone else sees ("This section is managed by the Project Manager", the incorrect view). This could be the root of the issue because the current user gets restrictions when they set them.

Also related is that "View restrictions are inherited, which means a restriction applied to one page will cascade down to any child pages. Edit restrictions are not inherited, which means pages need to be restricted individually." from <https://confluence.atlassian.com/doc/page-restrictions-139414.html#PageRestrictions-Howdoinheritedrestrictionswork?>

This is for server but this documentation does not exist for cloud. For the above example all users were set to have view and edit access and there was still this issue.

Any help with this would be greatly appreciated![2019_07_25_16_32_49_Access_Controlled_Plans_Confluence.png](https://community.atlassian.com/t5/image/serverpage/image-id/61495i126C7D69C857B471/image-size/large?v=v2&px=999 "2019_07_25_16_32_49_Access_Controlled_Plans_Confluence.png")![2019_07_25_16_36_02_Confluence.png](https://community.atlassian.com/t5/image/serverpage/image-id/61494i3499DFE91341377C/image-size/large?v=v2&px=999 "2019_07_25_16_36_02_Confluence.png")![MicrosoftTeams-image.png](https://community.atlassian.com/t5/image/serverpage/image-id/61496iCC2BCC0F89CE4572/image-size/large?v=v2&px=999 "MicrosoftTeams-image.png")


Answers:
author: Jack Vandemeulebroecke
body: This is currently a bug with the app involving groups with capital letters. <https://jira.atlassian.com/browse/CONFCLOUD-66969>


author: James Dellow
body: On the screenshot I noticed it says the page was created by Copy Page Tree - are the page permission set before or after you have copied the structure?

Also, how is the Child Display Macro configured?

comments: author: Jack Vandemeulebroecke
body: Hi James,

The restrictions on the pages were set after the page was created by Copy Page Tree, the space permissions I'm not sure about.

As for the Child Display Macro I doubt this is the issue because when users go to the parent page they cannot see the child pages so it would follow that they wouldn't be able to see child pages from the Child Display Macro. Here is how it is configured though.

Thanks![Untitled.png](https://community.atlassian.com/t5/image/serverpage/image-id/61594i861A9DA3F99E6E4F/image-size/large?v=v2&px=999 "Untitled.png")


author: James Dellow
body: Yes, if they can't see the child pages from the parent page, this should have nothing to do with the macro. Having said that, you shouldn't need to specify the Parent Page - the default is the current page. Is the Parent Page "Access Controlled Plans" actually the one in the same space or the space you copied it from?

However, assuming that it is pointing at the right parent page in the right space, can we see some sample page permissions from the child pages?


author: Jack Vandemeulebroecke
body: Hey James,

Just to update this, I created an Atlassian service request and was told this is a bug with the app involving groups with capital letters. <https://jira.atlassian.com/browse/CONFCLOUD-66969>

Thanks again for your help.


author: James Dellow
body: Thanks for the update [@Jack Vandemeulebroecke](/t5/user/viewprofilepage/user-id/3253166)

While I'm sorry to hear that you've been impacted by a bug, at least we know why now - I was really beginning to scratch my head about this one!