Assign scopes to create a reseller hierarchy

You can use a reseller hierarchy for billing, pricing, and to manage and aggregate your cloud costs and usage. To create a reseller hierarchy, assign scopes to reseller, key node, and reseller customer tenants. 

• Reseller: A reseller enterprise in the hierarchy can use partner or reseller credentials for public cloud (and create accounts and users for customers) and manage billing and pricing for their hierarchy. 

• Key node: A key node is the main enterprise for an organization, for example, the head office. A key node enterprise can obtain aggregate billing and usage data for their hierarchy

To define the hierarchy levels, use the Default scopes of the reseller, key node, and reseller customer enterprises.   

1. Go to Users → Enterprises
2. For the reseller and key node enterprises, create a scope
   1. Select an appropriate Parent scope, for example
      1. For a reseller, select the Global scope or no parent scope
      2. For a key node, select the reseller's Default scope as the parent scope
      3. For a sub-enterprise of a key node, e.g. a Department, select the key node's Default scope as the parent scope
3. Create or edit an enterprise to make it a Reseller or Key node enterprise
4. Set the appropriate scope as the Default scope for the enterprise. Abiquo will automatically add the enterprise to its Default scope
   
   • Note that if you change the default scope of an enteprise, Abiquo will not remove the enterprise from its previous scope
     

Administrators can share VM templates and VApp specs with users in scopes beneath their own Default scope in a hierarchy. Note that it is not mandatory to use resellers and key nodes in a cloud tenant hierarchy

• Basic scope hierarchy: The administrator for Spain could also have a scope hierarchy beneath the Spain scope that includes the scopes for Eastern Spain and Central and Southern Spain and then their customers at a lower level. The administrator for Spain can only manage the users of the Spanish national organization but they can share templates and Vapp specs with tenants in the scopes at all levels of the hierarchy.
  
  

   Click here to show/hide the hierarchy diagram