Allow Navigation to Subfolders When Using Upload Folder Presets in Asset Categories

[GhyferriH]

Is your feature request related to a problem? Please describe.

Currently, when an Upload Folder Preset is configured on an Asset Category, users are restricted to that specific folder and can only see the files located directly inside it.

This becomes problematic when customers maintain a structured asset library with multiple subfolders. Although the preset folder helps users start in the correct location, they lose the ability to browse deeper into the folder structure to find the assets they need.

(See attachment for current case)

As a result, customers are forced to either:

• Flatten their folder structure and store everything in a single folder, or
• Avoid using Upload Folder Presets altogether.

Both options negatively impact usability and asset management.

Describe the solution you’d like

Add a configuration option to Upload Folder Presets that allows administrators to choose the desired behavior.

For example:

☐ Restrict selection to preset folder only (current behavior)

☑ Allow navigation to subfolders starting from preset folder

This would allow users to start in the correct folder while still maintaining a structured asset hierarchy.

Describe alternatives you’ve considered

The current workaround is to remove the Upload Folder Preset entirely. This restores full folder navigation, but users must manually navigate through the entire folder structure every time they want to select an asset.

While functional, this reduces usability and increases the number of clicks required.

Additional context

Truvio Care confirmed that the current behavior is by design and that users are intentionally prevented from navigating away from the selected preset folder.

However, in many real-world scenarios, customers organize their assets in a main folder containing multiple subfolders. Being able to start in a predefined folder while still navigating into child folders would significantly improve the user experience without removing the existing restriction option.

Example structure:

Assets
├── Icons
│ ├── Brand A
│ ├── Brand B
│ └── Brand C

With the current implementation, users can only see files directly inside “Icons” and cannot access the subfolders.

2026-06-24.08-04-15.mp4