Am I able to limit the content tree to only showing folders? | Community
Skip to main content
dmescia2
dmescia2
Level 3
August 19, 2025
Solved

Am I able to limit the content tree to only showing folders?

  • August 19, 2025
  • 2 replies
  • 560 views

When navigating the Content Tree in AEM every time I open a folder in the siderail it shows the folders AND assets in that folder in the siderail. It shows the same thing in the results pane as well. Are we able to set up AEM to ONLY show the folders in the Content Tree side rail and not show the assets there? It makes it so much more difficult to navigate the folder structure when a ton of assets show up in it and there is no reason to see them in the siderail since I see them in the results pane.

Best answer by VishalKa5

Hi @dmescia2 ,

 

In AEM Assets, the Content Tree side rail is designed to display both folders and assets within a folder, and unfortunately there is no out-of-the-box setting to make it show only folders. This behavior is intentional, as the tree is meant to mirror the actual content structure. If you want to see only folders in the navigation, the main option is to implement a customization—for example, overlaying the UI or using clientlibs to filter the tree so it displays only folder node types (sling:Folder or dam:AssetFolder). As a workaround, many teams rely on the breadcrumb path or simply use the results pane (which already separates assets and folders more clearly) to navigate. In short, hiding assets from the side rail requires a custom UI filter, since it cannot be achieved through configuration alone.

 

Thanks & Regards,

Vishal

2 replies

VishalKa5
VishalKa5Accepted solution
Level 5
August 24, 2025

Hi @dmescia2 ,

 

In AEM Assets, the Content Tree side rail is designed to display both folders and assets within a folder, and unfortunately there is no out-of-the-box setting to make it show only folders. This behavior is intentional, as the tree is meant to mirror the actual content structure. If you want to see only folders in the navigation, the main option is to implement a customization—for example, overlaying the UI or using clientlibs to filter the tree so it displays only folder node types (sling:Folder or dam:AssetFolder). As a workaround, many teams rely on the breadcrumb path or simply use the results pane (which already separates assets and folders more clearly) to navigate. In short, hiding assets from the side rail requires a custom UI filter, since it cannot be achieved through configuration alone.

 

Thanks & Regards,

Vishal

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    September 2, 2025

    @dmescia2 just checking in! Were you able to get this resolved? If one of the replies above helped—whether it completely solved the issue or simply pointed you in the right direction—marking it as accepted can make it much easier for others with the same question to find a solution. And if you found a different way to fix it, sharing your approach would be a great contribution to the community. Your follow-up not only helps close the loop but also ensures others benefit from your experience. Thanks so much for being part of the conversation!

    Kautuk Sahni
    Terms & ConditionsAccessibility statement

    Loading footer...