For cardholder groups to be imported into Security Center, the database view or file for cardholder groups must follow the Card Synchronization schema.
- Including pictures increases the amount of time it takes to import.
- In database views, all mandatory and optional columns must be included.
- If you have additional columns, map them to custom fields.
- In delimited text files, optional columns can be excluded.
|UniqueId||String||The unique ID of the cardholder group. The unique ID can be an alphanumeric code, an email address, or a Security Center GUID.|
|Name||String||The name of the cardholder group.|
|String||The email address of the cardholder group.|
The following image is an example of a cardholder groups view in a Microsoft SQL Server database.