Scope concepts table

• A list of resources (enterprises and/or datacenters) to allow access

For example, Scope AB: DatacenterA, DatacenterB, Enterprise1, Enterprise2, Enterprise3.

• The list of resources (datacenters and enterprises) that the user can view and manage.

• The user must also have the other required permissions (privileges and allowed datacenters)

• A user can work in allowed datacenters (e.g. create virtual datacenters, deploy), even if the datacenters are not in their scope.

• An Administrator can manage users of the enterprises that are in their scope

• The list of enterprises whose users can access a resource, if they have the other required permissions

• Administrators select a set of scopes to share a resource with users of the enterprises listed in the scopes

Used to share VM templates and VApp specs. An administrator can select their own scope, and scopes underneath their scope in the scope hierarchy

• A parent scope and one or more child scopes

• Used for sharing resources to tenants that are underneath the administrator's scope
  
  
  

Administrators can share VM templates and VApp specs with users in scopes beneath their own scope. But they cannot manage the enterprises that are not directly in their user scope

• The default scope for the cloud administrator that always includes all resources and cannot be modified

• The global scope

• Use all enterprises checkbox selected - ALL current and future enterprises

• Use all datacenters checkbox selected - ALL current and future datacenters

An unlimited scope has new resources added automatically in its unlimited dimensions. Only a user with an unlimited scope can create an unlimited scope in the same dimensions as their scope.

• When a user creates a pricing model, the platform assigns the user's scope for tenants.

• Only users with the same tenant scope can manage the pricing models

• All users with pricing privileges can view the pricing model of their tenant

• You cannot change the pricing scope or display it in the UI