Global cardholder management rules and restrictions

The are some rules and restrictions that apply when using Global cardholder management.

Before you start globally managing your cardholders, read the following rules and restrictions.

Rules concerning local and global partitions

Rules concerning local and global entities

BEST PRACTICE: It is always recommended to apply access rules to cardholder groups rather than individual cardholders. For this reason, it is recommended to share the cardholders along with their parent cardholder groups. If this is not feasible for any reason, then we recommend that you create a local cardholder group for the global cardholders.

Rules concerning global custom fields and data types

BEST PRACTICE: If you are to implement GCM within your organization, we recommended that you define all custom fields and data types for global entities on the sharing host.

Rules concerning Federation™ and global entities

Rules concerning Active Directory and global entities

CAUTION: Although it is possible to modify global cardholders and cardholder groups imported from an Active Directory on the sharing guest, these changes are temporary. You lose the changes you made when the sharing host synchronizes with the Active Directory.
BEST PRACTICE: If all cardholder data entry must be centralized, the system that imports cardholders from your corporate Active Directory should act as the sharing host, and all modifications must be made using the directory service.