FR: Community account: Shares census, reshare control and notifications

In some cases, an account is used for a group of individuals to host their project's resources. Project has its account and each individual too. Project's account do share main folders (and calendars, contacts, etc.) to each individual.
Individuals can reshare temporarily concrete subfolders to "3rd users" that can not be members of same project. Same as share links.

Problem is Each account can see what this individual has been reshared to others, but collective account (project's main) not. From project's account the only shares that can see are first-step ones and not those that next users reshared.

I ask for diverse solutions for this scenario, to allow individuals manage a collective account:

• A Nextcloud account can see and manage their own shares + other's reshares from it.
• A Nextcloud account can share in an "admin/delegated" mode: Sharing receptor can see and manage other's reshares within same resource. On resharing action, notification will be sent from delegator account (collective project in example).

As an alternative (not exclusive), a collective account would be completely delegated to be administered by other users. Instead of having to login with common account, any of the authorized users by that account could "impersonate" or make full actions in the name of collective account.

The issue names no files, tests, or implementation entry points. First clarify which delegation, reshare visibility, notification, and impersonation behavior is required; done should be defined as an agreed design with specific permission and notification rules before code can be located.