Permission on Experience Fragment

[Shaheena_Sk]

Hi,

I provided allow permission to create to /content/experience-fragment and save it. On expanding the path i noticed the permission automatically came down to /content/experience-fragment/<folderName>. But the experience fragments below that still remained denied. According to my understanding the permissions should have come down to the lowest level from the parent. But, that is not true in this case. The permission is getting applied to the child folders under /content/experience-fragment (even if there are n number of folders), but its not getting applied to the experience fragments under the folders (should happen automatically just like it happening for folders, but i had to do it manually). 

Added another XF called xyz and yet the permission didnt get propageted to it.

What is the justification to this behaviour?

[Nikhil-Kumar]

@Shaheena_Sk 

I see similar issue at https://github.com/Netcentric/accesscontroltool/issues/368
Not sure what's the reason is.

[Shaheena_Sk]

everytime we have a new XF, we have to go and provide the permission there. which makes things very difficult

[Nikhil-Kumar]

@Shaheena_Sk 

I think this is the expected behavior, because if you refer my structure when I gave permission to the root folder it went until the follder where I have the experince fragment page which is using exp fragment template. So which by defaults provides permission to it's child as well.

You no need to check the checkbox for the permission to these pages with exp frag template.

If you verify the access it should work with that user.

Thanks,
Nikhil

[Shaheena_Sk]

yes, u got me right! the permission are coming till folder, but not till the experience fragment. i have to provide the permission to the experience separately later. so, next time if i create another experience fragment then again i have to provide the permission to those. is there any reason behind such a behaviour?

[arunpatidar]

Did you check the XF templates initial node? do you have any rep:policy there?

Can you check master node from crx/de and check what is added if you create new xf.

[Shaheena_Sk]

I am using the We.Retail templates to create my XF. And, the rep:policy exists under /content/experience-fragment with the same permissions that we can see under useradmin. rep:policy nodes doesn exist under any sub folder under the path /content/experience-fragment. And if i create a new XF, then the permission from parent is not getting propagated to the the XF.

[Shaheena_Sk]

edited my question and attached 2 more screenshot based on ur comment

[arunpatidar]

Thanks for the screenshot. What user are you using? is user part of experience-fragment-editor? because this group looks fine

[Shaheena_Sk]

i created a group called cutom-author, this is a member of OOTB content-author. And my test user is a part of the custom group that i created.

[Shaheena_Sk]

The strange part is, if i give permission to /content/experience-fragment, it propagates to all the child folders and even the XF only when i have provided delete permission. But if i remove the delete permission, the modify permission from XF goes away and it is only present till the folder level under /content/experience-fragment/folders

[arunpatidar]

yes you need to set both delete and modify actions.