| Excerpt |
|---|
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 multiple levels. |
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 IT department in the head office and the IT department in the regional office may both share templates with the stores.
The following diagram shows an example of a scope hierarchy. An administrator with the scope "Multinational" would manage the users and templates of the enterprises "Multinational", "National1" and "NationalN".
A user with the scope "National1" would manage the users of "Nat1Sub1" to "Nat1SubN". And they could also share templates and blueprints with users in the scopes beneath their scope, which would be "Nat1Sub1".
To create this structure, first create the "Multinational" scope and add the enterprises ("National1" and "NationalN"). The parent of this scope can be the Global scope. Then create the "National1" scope. Set the parent scope of the "National1" scope as "Multinational". And add the enterprises ("Nat1Sub1" and "Nat1SubN").
Next create the next scope "Nat1Sub1" and set its parent scope as "National1". Then add the enterprises ("N1S1Dept1" and "N1S1Dept2"...).
Note that it is possible that an administrator will not need to have their own enterprise in scope. In this case they will still be able to access the Apps library but they won't be able to edit the public cloud credentials or users.
The enterprise at the top of any hierarchy will be the key node for data aggregation. In the above example, "Multinational" would be a key node in its scope and scope hierarchy. To mark the key node, edit the tenant that represents the head office or equivalent, at the top of the scope hierarchy, and set its scope as the default scope 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.
For more information about scopes see:
...