System Settings

The Customer Information section displays the following information:

Customer ID - This shows one of the unique IDs for the Customer Account. This is mostly useful for the PDK Support staff.

System ID - This shows one of the unique IDs for the Customer Account. This is mostly useful for the PDK Support staff.

System Name - This displays the name of the Customer Account. This can only be changed by the Dealer Partner with the Integrator Permission role in their Dealer Account.

Description - Selecting in this field allows a Partner to enter a description for the Customer Account.

Industry - From the dropdown list, select the Industry Type for the Customer Account.

Install Type - From the dropdown list, select whether the install type is New Install or Replace/Upgrade Existing System to PDK for the Customer Account.

The use of Mobile Button digital credentials can be restricted to a Geofenced boundary. Add the address of your Customer's Location by entering it manually in the Street Address field, using your current location, or dragging and dropping a pin. More information regarding Geofencing can be found here.

Admins can set a direct point of contact for their End Users who need support. For more information regarding Mobile App Support setup, can be found here.

Region - Select the Region of the World where the Customer Account's default Time Zone is located.

Time Zone - Select the default Time Zone for the Customer Account. All Cloud Nodes that are added to the Customer Account after the Time Zone is configured or changed will be added to the Customer Account. This can be changed in the General tab on the Configuration page.

Continuity allows a local version of the access database and rules to be retained on Cloud Nodes and Red-series controllers. This will allow credentials and schedules to function as expected for a designated period when communication with the Internet (Cloud Node) or the Cloud Node (Red-series Controller) is lost.

If the Cloud Node loses connection to the Internet, the local Cloud Node database and attached Controllers will function as normal for the 'Time before Ecard fall-back' setting. At that time, the local database will be disabled until the Cloud Node can connect to the Internet and sync again.

If a Red-series Controller is very briefly offline (60 seconds or less), any Events triggering rules from the Controller will be processed when the Controller reconnects, thus appearing to be delayed. If the Controller is offline for longer than this, only rules triggering emails will be processed.

Please note that while a Controller is operating in Continuity mode, the following restrictions will occur:

• Elevator access on the Controller will not function.
• You will be unable to activate doors/devices connected to the Controller from inside the PDK Access app. Bluetooth and hard credential access are unaffected.
• Any Events that occurred on the Controller while in Continuity mode will not be available in the Reports dashboard until the Controller reconnects and synchronizes data with the Cloud Node.
• Any emails from Event rules on the Controller that occur while the Controller is in Continuity mode will not be processed until the Controller connects to the Cloud Node.

When configuring Continuity, the following settings are available:

Time before Ecard fall-back - This allows you to select the period during which the Cloud Node and/or Controller will operate in Continuity Mode before reverting to using only Ecards.

Schedule access if time is unknown - This setting specifies which People will have access to the connected doors/devices if the Controller cannot validate the current time (such as being unable to connect to the internet entirely) while operating in Continuity mode. If the Controller can validate the current time, it will operate as expected in Continuity mode.

• Ecards Only: The controllers will respond only to Ecards, effectively bypassing Controller Continuity mode.
• People with 24x7 Access: This will only allow people with 24x7 access to the door to use their credentials, while unable to validate the current time
• Ignore Schedules: All those with access to the door are granted entry regardless of the schedule.

Activate Card Format - Tap or click Activate Card Format to select the additional Card Format(s) that will be applied to all Cloud Nodes in the Customer Account by default. This can be changed in the Cards tab on the Cloud Node's Configuration page.

Manage Custom Formats - Tap or click the Manage Custom Formats button to view, add, or edit an existing Card Format.

Monthly Credential Resets per User - Selecting this field allows a User to adjust the number of times an End-User can request replacement Mobile Credentials per month before the End-User must contact the Customer Account representative to reset the restrictions on requesting replacement credentials.

Enable issuance of Bluetooth Credentials - Tap or click the toggle switch to enable or disable this feature.

Enable issuance of Mobile App Credentials - Tap or click the toggle switch to enable or disable the feature that allows issuing PDK Access Mobile Button credentials.

Activate Card Formats

Cloud Nodes can use one or more Card Formats for your physical credentials.

In the Configuration tab of the Config window, you can choose from the available Card Formats on the Cloud Node or create a new one.

Notes:

• Different reader models may send slightly different bit results with the same card.
• Red-series controllers report the bit range properly, but older controllers (Single IO and Eight IO) may require a larger bit range compared to Red-series controllers.
• The limit for Active Card Formats is five (5) formats.

• Yellow Formats are Card Formats created by ProdataKey and shipped with the Cloud Node
• Blue Formats are Card Formats added through the "Formatter defined by parameters" option described below.
• Grey Formats are Card Formats uploaded through the "Custom Formatter module" option described below.

Selecting an existing card format

Tap or click the plus icon next to Active Card Formats. The Activate Card Format drawer will appear, allowing you to create a new Card format.

After configuring the Card Format, tap or click the Save button to add the Card Format to the Cloud Node.

Edit an Active Card Format

To edit a Card Format, tap or click on the Card Format in the list. For the default included Card Formats, the Format can not be edited. For newly created Card Formats, refer to the section below regarding adding a new Card Format.

By clicking the Manage Custom Formats button, you are able to add, view format details, or delete User-Defined Card Formats.

Adding a Custom Card Format

Tapping or clicking the Add button in the bottom-right corner of the Active Card Formats menu opens the Add Card Format window.

From this menu, you can either upload a JavaScript module using the Upload button in the lower left corner or manually enter the parameters for the Card Format, as explained below.

• Name - Enter a unique name for the Card Format
• Num Bits - This is the number of bits in the Card Format. Any bit data in the credential scan above this value will be ignored.
• Cardholder ID Bits - The number of bits for the card number.
• Cardholder Start Address - This is the bit in the credential scan where the card number begins.
• Num Facility Code Bits (Optional) - This is the number of bits for the Facility Code of the credential.
• Facility Start Address (Optional) - This is the bit in the credential scan where the Facility Code begins.
• Num Bits to Sum For Even Parity (Optional) - This is the bit length from the credential scan used to determine even parity.
• Even Start Address (Optional) - This is the bit in the credential scan where the even parity bits begin.
• Num Bits to Start For Odd Parity (Optional) - This is the bit length from the credential scan used to determine odd parity.
• Odd Start Address (Optional) - This is the bit in the credential scan where the odd parity bits begin.
• Default Min Input Bits - Enter the minimum bits for the Card Range
• Default Max Input Bits - Enter the maximum bits for the Card Range
• Support Facility Code Processing - Select if the Facility Code bits are used for this Card Format
• Supports Parity - Enforces a secondary check of data from the scanned credential to ensure a misread credential is not processed as valid.

Units are designed for Residential Properties, such as apartment complexes. They allow Admins or Managers to efficiently manage resident access without creating manual Access Rules for each apartment. Before Units can be created, this must be enabled in System Settings.

The Reporting feature offers three different pricing plans, each with distinct data retention timeframes, Saved Report storage limits, and Saved Report retention timeframes. The 'Reporting Plan' options can be changed by clicking into System Settings.

Report Retention - This is the length of time that Report data is saved on the Customer Account.
Saved Report Storage - This is the amount of data that Saved Reports can occupy on the Customer Account.
Saved Report Retention - This is the length of time that Saved Reports are retained on the Customer Account.

The Small Business level Billing Plan is included on all Customer Accounts by default. For additional information regarding the different billing plans, please contact the ProdataKey sales staff.

The Demo System section (visible only to dealers with the Integrator Permission role) allows a single Customer Account on a Dealer Account to be configured as a Customer Account with a limited number of non-billable Devices for the Installation Partner's use in demonstrating the ProdataKey software.

The System Management section allows an Installation Partner with the Integrator Permission Role to permanently delete a Customer Account and all associated data from the Dealer Account.