option for COU parent child relationships to affect delegation of privileges

Some organizational structures can be naturally reflected as nested COUs with parent-child relationships. In such instances it would be helpful to have an option, probably at the CO level, for the various Registry privileges, data models, and features to respect the parent-child relationship and delegate in the way that many people seem to expect.

So for example if a CO Person is a COU admin for COU 1 and COU 2 is a child of COU 1 then the CO Person should also be a COU admin for COU 2.

If an enrollment flow can only be executed if a CO Person is a COU admin for COU 2 and COU 2 is the child of COU 1 then any COU admin for COU 1 should be able to execute the flow.

If a CO Person has a role in COU 2 and therefore a membership in COU 2:members and COU 2 is a child of COU 1 then the CO Person should automatically have a role in COU 1 and a membership in COU 1:members.