...
The following diagram shows an example of a scope hierarchy.
It
A user with the scope "National1" would manage the users of "Nat1 Reseller 1" to "Nat1 Reseller N". And they could also share templates and blueprints with users in the scopes beneath their scope, which would be "N1 Reseller1" and "N1R1Ent1".
To create this structure, first create the "National1" scope and add the enterprises (Nat 1 Reseller 1"...). Then create the next scope "N1 Reseller1" and set its parent scope as "National1". Then add the enterprises ("N1R1 Ent1 IT team"...). And so on.
Note that it is possible that a customer's administrator will not need to have their own enterprise in scope. In this case they will still be able to access the enterprise's Apps library but they won't be able to edit the enterprise's public cloud credentials or users.
If you create a scope hierarchy for a multi-enterprise tenant, then The enterprise at the top of the hierarchy will be the key node for data aggregation. In the above example, National 1 would be a key node.
To mark the key node, edit the tenant that represents the head office or equivalent, which would usually be at the top of the scope hierarchy, and using the set its scope as the default scope , and for the enterprise. Then select the Key node option.
...
This tenant will be marked with a (K) in the tenant list, indicating that the enterprise is a key node.
The platform will mark the Key node with (K) in the Enterprise list, as shown in the screenshot in the Reseller section.