PDK io People Settings Overview
Table of Contents
Click the People icon in the Cloud Node Appliances home screen to add people to a node as well as to view/edit people already assigned to a node. People who have been created previously are listed in the People screen in alpha order by last name.
NOTE: To edit (or view) the information for people who have already been assigned to a node, click on a name in the People screen and reference the field headings found below, in order to edit the field information for the person.
To add a new user, click the + icon in the lower right of the People screen.
SINGLE Tab - Add Person Screen
Use the default SINGLE tab in the Add Person screen to add new people one at a time.
Enter the First Name and Last Name of the person being added. Click ADD.
When new users are added, the Person screen is displayed.
The First Name and Last Name of the user is shown in this Person screen.
Partition - Person Screen
The Partition field only appears if a partition or partitions have been created previously. If this person being added is to be assigned to a partition, click inside this Partition field or on the down arrow to select a listed partition. (See Partitions for additional information.)
NOTE: A Default partition exists but the Partition field does not appear until after an initial partition is created.
RECENT AUDIT LOGS - Person Screen
Click RECENT AUDIT LOGS (in the top right of the Person screen) to view the Recent Audit Logs screen. The audit log screen provides an account of changes and shows system activity from controller events, commands, additions, and modifications to access control devices, the device names, and the names of persons who caused those events and changes.
NOTE: This Recent Audit Logs list only shows the ten most recent events. If desired, the Reports feature can be used to view all logged events and modifications for a specific time period, by device name, user names, etc.
ALL and MODIFICATION Tabs
ALL - Shows all of the ten most recent commands and filtered results that have occurred for the available devices.
MODIFICATION - Shows the ten most recent modifications made to doors and elevators by device name, rules and groups used, and the names of those making changes.
By clicking on each of the column headings (Occurred, Info Text, Event, and Result), an edit field opens that enables entering search text on which to filter and refine the contents of the listed column topic. This can be useful when there is a specifically desired list of audit log items needed for a particular date and time, specific text content, a particular event, or a result.
Click on the column heading and enter the text to search on within that column.
Date and time when the event occurred in the form: YYYY-MM-DD HH:MM:SS (Year, Month, Day, Hour, Minutes, Seconds)
Information on the person / device / input that was affected by the addition / modification.
A brief description of the added or modified event that occurred. (For example: Entity Modified or Entity Added)
The result, if any, of the event.
To the far right of each log entry is the DETAILS link. Clicking the DETAILS link displays a Log Entry Details informational window showing the Card Number / Group Name / Person Name.
Click REFRESH to update and display the most recent Audit Log additions / changes / updates.
IMPORT Tab - Add Person Screen
Use the IMPORT tab in the Add Person screen to import a list of people and cards through the use of a CSV file. If a list of users exists from another application in the form of a CSV file, multiple users can be imported (for a maximum of 1000 records), eliminating the need to add each person individually, one at a time.
NOTE: Importing is most effective when adding a large batch of people and cards at one time. Listing an existing group in the Group column of the CSV spreadsheet file adds the person to the group. Entering a group that does not yet exist will create that group as a new group and adds each of the persons to that group.
Populate the spreadsheet file with a list of people and cards to be imported into the system. Save the spreadsheet file as a .csv file.
NOTE: Be sure any duplicate first and last names and card numbers in the CSV file are eliminated. Duplicate names and card numbers are not imported. Legitimate duplicate names need to be added manually.
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.
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.
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.
Click Open to import the file.
Click ADD in the IMPORT tab of the Add Person screen to accept and begin the import process.
In the People screen, hover the cursor over the user to be deleted and click the trash icon. Once a person is deleted from the system, their information is unrecoverable.
NOTE: Assigning a person to a blank group is an easy way to revoke access without deleting their information from the system. Adding them back into a group will instantly restore their access rights.
Integrating Comelit with PDK io
PDK and Comelit Database Integration Overview
1. Click on a customer name listed in the Customers section of the screen (also containing the Cloud Nodes and Permissions sections) in order to edit the customer's information and ultimately integrate it with Comelit data.
2. Click the Edit icon.
3. Check the Comelit option in the Available Intercom Connections section.
4. Click SAVE.
5. Click on the same Customer.
6. In that customer's screen, click on the Cloud Node associated with this customer.
7. From the main dashboard, click Configuration .
8. In the Configuration screen, click the CONFIG tab.
9. At Video Intercom Connections, click the + icon.
10. In the Add Connection screen, click on the in the Comelit ID32 field and follow the indicated instructions for the required Comelit ID32 information.
11. Assign a name in the Name field.
12. In the Login section, enter your Comelit Username and Password. Confirm the password and click ADD.
13. Click on the PDK logo at the upper left of the screen to access the PDK io main dashboard again and select People .
NOTE: It is here, in the People feature of PDK io, that you will be adding each of the individuals that will be associated with a Comelit Unit or apartment. In essence, the people that are registered in the PDK io application can be selected and assigned to their respective Comelit apartment or Unit; in the steps that follow, you will link the appropriate person from PDK io with their Comelit apartment (or Unit).
14. In the People screen, click on a person that is to be linked to and associated with their apartment, or Unit information from the Comelit application.
15. In the Person screen, click the + icon to the right of Video Intercom Links to view the Add Link screen.
Intercom Connection - Click in this field or on the down arrow to select the connection (person's) name.
Unit - Click in this field to select the apartment unit that should be associated with the person named in Intercom Connection.
Phone Number - Enter that person's phone number to be associated with the Unit (apartment).
PDK and Comelit Tenant Integration Overview
16. Click SAVE. A green dot indicates that the PDK io and Comelit information has synced and is working as it should.
17. Repeat this process for each person that needs to be added and assigned to a Comelit apartment, or Unit.
See the article: Integration Features with PDK io for specific instructions.