In a traditional View environment, you use View Administrator to create entitlements. These local entitlements entitle users and groups to a specific desktop pool on a View Connection Server instance.
In a Cloud Pod Architecture environment, you create global entitlements to entitle users or groups to multiple desktops across multiple pods in the pod federation. When you use global entitlements, you do not need to configure and manage local entitlements. Global entitlements simplify administration, even in a pod federation that contains a single pod.
View stores global entitlements in the Global Data Layer. Because global entitlements are shared data, global entitlement information is available on all View Connection Server instances in the pod federation.
As a best practice, you should not configure local and global entitlements for the same desktop pool. If you use both types of entitlements for the same desktop pool, the same desktop might appear as both a local and a global entitlement in the list of desktops that Horizon Client shows to an end user.
Each global entitlement contains a list of member users or groups, a list of the desktop pools that can provide desktops for entitled users, and a scope policy. The desktop pools in a global entitlement can be either floating or dedicated pools. You specify whether a global entitlement is floating or dedicated during global entitlement creation.
A global entitlement's scope policy specifies where View looks for desktops when it allocates desktops to users in the global entitlement. It also determines whether View looks for desktops in any pod in the pod federation, in pods that reside in the same site, or only in the pod to which the user is connected.