Some large customers may require a hierarchy of tenants on the platform (i.e. a tree of multiple enterprises). These tenants can have their own scope hierarchy with the customer's scope and their departments, and their scopes and sub-departments, and so on, in scopes underneath the customer's scope.
An example of this would be customer that is a chain of retail stores with a head office and regional offices, as well as the stores themselves. The head office may manage the regional offices, and the regional offices may manage the stores.
The following diagram shows an example of a scope hierarchy.
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 edit the tenant that represents the head office or equivalent, which would usually be at the top of the scope hierarchy, and using the scope as the default scope, and 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.See Abiquo cloud reseller hierarchy