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?
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.
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.