Permission on Experience Fragment | Community
Skip to main content
S
Shaheena_Sk
Level 4
August 26, 2020

Permission on Experience Fragment

  • August 26, 2020
  • 3 replies
  • 3739 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Nikhil-Kumar
Community Advisor
Nikhil-KumarCommunity Advisor
Community Advisor
August 26, 2020

@shaheena_sk 

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

    S
    Shaheena_SkAuthor
    Level 4
    August 26, 2020
    everytime we have a new XF, we have to go and provide the permission there. which makes things very difficult
      Nikhil-Kumar
      Community Advisor
      Nikhil-KumarCommunity Advisor
      Community Advisor
      August 26, 2020

      @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

       






        S
        Shaheena_SkAuthor
        Level 4
        August 26, 2020
        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
          Community Advisor
          arunpatidarCommunity Advisor
          Community Advisor
          August 26, 2020

          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.

          Arun Patidar
            S
            Shaheena_SkAuthor
            Level 4
            August 27, 2020
            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.
              Terms & ConditionsAccessibility statement

              Loading footer...