DAM folder not visible in assets UI | Community
Skip to main content
jezwn
jezwn
Level 5
June 24, 2021

DAM folder not visible in assets UI

  • June 24, 2021
  • 2 replies
  • 1983 views

I've this folder in DAM, named xyz where I've the permissions to Read, Modify and Delete. When checking the assets UI this folder is not visible <domain>/assets.html/content/dam. If I hit the URL at <domain>/assets.html/content/dam/xyz I have the persmissions as above. I have checked with other folders as well inside DAM, some other folders are also having the same issue with these given permissions.

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

2 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
June 24, 2021

@jezwn What is the version of AEM are you using? Please check the permissions of parent folder as well, as child folders/nodes will be read relative to parent folder.

    jezwn
    jezwnAuthor
    Level 5
    June 24, 2021

    @shashi_mulugu  The AEM version we're using is 6.5.4. The parent folder does contain these three permissions. One thing I observed later is there's a cloud config(/conf/global) to these folders which are not visible and no permissions has been set for /conf/global, which I assume would be the cause. But there's one outstanding folder with this cloud config and is visible in the assets UI. The only difference I see in the node properties is that, this one contains a property called 'sourcing' which is set to false.

    Ritesh_Mittal
    Community Advisor and Adobe Champion
    Ritesh_MittalCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    June 24, 2021

    @jezwn ,

     

    It might be because one of the content node under DAM is corrupted. Please check if you have jcr:content node under DAM. Also, check if you are getting error in browser console/network tab or in error logs.

     

      jezwn
      jezwnAuthor
      Level 5
      June 24, 2021

      @ritesh_mittal  The issue is only with certain users. One thing I observed later is there's a cloud config(/conf/global) to these folders which are not visible and no permissions has been set for /conf/global, which I assume would be the cause. But there's one outstanding folder with this cloud config and is visible in the assets UI. The only difference I see in the node properties is that, this one contains a property called 'sourcing' which is set to false.

        Terms & ConditionsAccessibility statement

        Loading footer...