Customize visibility logic in hierarchical client structures

In our 123erfasst structure, we work with multiple clients or levels within a hierarchy. Currently, data visibility is not implemented consistently from our perspective:

Users created in a subordinate structure can apparently view users from higher-level structures in both the app and the web version. Conversely, however, in the web version, users in a higher-level structure cannot view requests from the structures below them, for example.

From a business perspective, the logic should work differently:

• A parent structure should be able to view all data and processes in the child structures.

• A subordinate structure should not have access to people or content from parent structures.

Desired behavior:
Visibility should consistently follow the hierarchy: fully visible from top to bottom, but not from bottom to top.

Benefits:
This would make the rights and visibility structure logical, transparent, and compliant with data protection regulations.