Display cross-module relationships in a single tree view

Users want the navigation tree to reflect relationships across multiple modules at once, so that connected data — such as categories, products, and variants — can be explored in a single, familiar structure. Problem / Pain: The current tree navigation is limited to one module at a time. In PIM workflows, however, related data — such as categories, products, and variants — is maintained across several modules that reference each other. Because the tree does not reflect these relationships, users cannot see the full structure in one place. This makes it harder to navigate, understand data context, and work efficiently — especially for users who expect a connected product hierarchy as a standard experience. Impact / Benefit: A tree view that spans multiple related modules would give users a clearer, more intuitive picture of how their data is structured. It would reduce navigation effort, shorten the time needed to find or contextualize information, and lower the learning curve for new users unfamiliar with how modules relate to each other. Example use case: A PIM manager wants to navigate from a product category down to individual products and their variants in one continuous tree structure, without switching between separate module views to piece together the full hierarchy. Idea source: Customer feedback Voting note: Vote for this idea if this need is relevant to you as well.