Configure module and product explorer views directly in the admin interface

Admins want to create and manage explorer views for modules through the admin interface, so that the hierarchical navigation experience can be set up and maintained without requiring database access or technical intervention. Problem / Pain: The module and product explorer is a powerful navigation feature that allows users to work within familiar hierarchical structures and navigate between objects without switching modules. However, the views required to enable this experience can currently only be created through XML configuration files and direct database access. This means the explorer is technically available in the product but practically unusable without developer involvement, and admins have no way to set it up or maintain it independently. Impact / Benefit: Being able to create and configure explorer views through the admin interface would make the module and product explorer fully accessible as a standard product feature for the first time. Admins could enable and tailor the hierarchical navigation experience per role without any technical intervention, making the explorer a practical and maintainable tool for PIM workflows where hierarchical thinking is the norm. Example use case: A PIM admin wants to give a specific user role a product explorer view that reflects the product hierarchy used in their daily work. Currently this requires database access and XML configuration. With admin interface support, the admin could select the relevant module, choose the appropriate view option, and save the configuration directly making the explorer available to that role immediately without any technical involvement. Idea source: Internal suggestion Voting note: Vote for this idea if this need is relevant to you as well.