In cases where a list of users exists from another application, multiple users (up to a maximum of 1000 records) can be imported in the People application of pdk io using a spreadsheet-style .csv file.
Such a file can also be created in a spreadsheet application and saved as a CSV file. Creating and importing a CSV file eliminates the need to add each person individually, one user at a time. The spreadsheet file must be populated with the necessary information in order to be successfully imported into the system. Save the spreadsheet file as a .csv file.
IMPORTANT: If you are not using ALL of the columns when importing the CSV file, delete the columns that are not being used or you will get errors and the information in the CSV file will not import.
The image below illustrates the required format for such a .csv file.
NOTE: The header information in row 1 (First Name, Last Name, Card, Groups, Email, Touch, and Token) MUST be included in the file otherwise the file import will fail and the information will not import. User information for each column should be completed in subsequent rows 2, 3, 4, etc. If you will NOT be using either the email, or the touch, or the token options for ANY of the users in the CSV file, that column can be eliminated altogether from the CSF file.
Selecting DOWNLOAD CSV TEMPLATE in the Add Person screen downloads a spreadsheet file named import_person_template.csv that can be used as a template. This spreadsheet can provide the ability to easily transfer a people database from one Cloud Node to another.
For an existing CSV file with name and location information, click SELECT CSV to browse to the file’s location and import the file in the following format.
NOTE: The header information in row 1 MUST be included in the file, otherwise the file import will give an error and the information will not import.
First Name - User's first name.
Last Name - User's last name.
Cards - Reader card's assigned unique ID number.
IMPORTANT: Be sure any duplicate First and Last names and Card numbers in the CSV file are eliminated. Duplicate names or card numbers will cause the CSV import to fail; legitimate duplicate names or duplicate card numbers must be added manually.
Groups - Group or groups the user is assigned to or will be assigned to after the file is imported.
NOTE: If a user is assigned to one or more groups in the Groups column of the CSV file and that group has not been created prior to the import, that group (or groups) is created and the user is assigned as part of that group after the import of the CSV file.
Email - User's company or personal email address through which the user may be contacted.
NOTE: If the Email column is used, then an email address MUST be used for EACH user. If one email cell is left blank in any row, the import will fail.
Touch - An integer stating how many Bluetooth credential invites you would like sent to this person on import. Maximum 5.
Token - An integer stating how many mobile credential invites you would like sent to this person on import. Maximum 5.
Enabled - Whether this person's account should be enabled or disabled. 1 means the account is enabled. 0 means the account is not enabled.
Pin - PIN numbers
NOTE: Using a leading zero at the start of a PIN will drop that 0 digit when it is used in PDK. A PIN with a leading zero shouldn't be used. As an example, if a PIN of 0123 is created and entered into the reader, the system will see it as 123. Zero is a non-significant digit and is dropped at the start of a number. The system will not recognize a PIN number with a leading zero as a valid PIN and will not allow it.
Duress Pin - Duress PIN numbers
Partition - Partitions that have been created
NOTE: All cells must be filled in; if any cell in the column is left blank, the import will fail.