Organization hierarchy in hybrid cloud

Multicloud platforms may have a hierarchy of tenants in a tree structure. These tenants can have their own scope hierarchy with multiple levels.

An example of a hierarchy of tenants could be 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 IT department in the head office and the IT department in the regional office may both share VM templates with the stores. 

Tenant hierarchy example

You can use tenant scopes to:

1. Create restricted sets of resources for administrators
2. Share resources with a group of tenants and an optional tenant hierarchy

The following diagram shows an example of a tenant scopes that are in a hierarchy. The hierarchy contains the following scopes:

1. Multinational scope
2. National1 scope
3. Nat1Sub1 scope

Manage enterprises in scope

When an enterprise is in your user scope, you can manage the enterprise and its users and resources such as VM templates, depending on your user role and privileges.

An administrator with the Multinational scope would manage the enterprises:

1. "Multinational"
2. "National1" 
3. "NationalN".

An administrator with the National1 scope would manage the enterprises:

1. "Nat1Sub1"
2. "Nat1SubN".

Share resources to enterprises in a scope beneath your scope

When an enterprise is in a scope beneath your scope, you can share resources with the users of the enterprise. For example, you can share VM templates and configuration blueprints.

• An administrator with the Multinational scope could share templates and blueprints with users in all of the enterprises.
• An administrator with the National1 scope could share to the enterprises in the scopes beneath their scope, which means the Nat1Sub1 scope.

How to create a scope hierarchy

To create a scope hierarchy:

1. Create the top level scope, which can have the Global scope as its parent
2. Add the enterprises in the top level scope
3. Create the second level scope and set the parent scope to be the top level scope
4. Add the enterprises to the second level scope
5. Continue to the next scope level, assign the parents
6. Add the enterprises 

Continue to create scopes and add enterprises for the rest of the hierarchy

For the above example

1. Create the "Multinational" scope. The parent of this scope can be the Global scope
2. Add the enterprises ("National1" and "NationalN"). 
3. Create the "National1" scope. Set the parent scope of the "National1" scope as "Multinational". 
4. Add the enterprises ("Nat1Sub1" and "Nat1SubN").  
5. Next create the next scope "Nat1Sub1" and set its parent scope as "National1". 
6. Then add the enterprises ("N1S1Dept1" and "N1S1Dept2"...).

Configure a key node at the top of the hierarchy for data aggregation

The enterprise at the top of any hierarchy can be set as the key node for data aggregation. In the above example, "Multinational" would be a key node in its scope and scope hierarchy.

To mark a key node:

1. Edit the tenant that represents the head office or equivalent, at the top of the scope hierarchy
2. Set the top level scope as the default scope for the enterprise. This will be the scope where the enterprise is the key node
   1. The platform will also apply the default scope to new users in this enterprise, but you can edit this scope, for example, to set a scope with only the user's enterprise
3. 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.

For more information about scopes see: 

• Manage Scopes
• Manage resource scopes