Overview 

FelixGate integrates directly with PDK to provide access-control data to the FelixGate tailgating detection platform. 

The integration allows FelixGate to receive access history events from PDK for configured door entry points. These access events are matched against FelixGate's door activity and video analytics to determine whether a person entering the facility has presented a valid credential. 

Integration boundary: FelixGate operates alongside PDK. It does not control or modify access permissions, unlock doors, or make changes to the customer's PDK configuration.

PDK remains the access-control authority. FelixGate receives and correlates access events only. 

How the Integration Works 

1. FelixGate Tailgating Hardware 

The customer purchases and installs FelixGate hardware at the required facility entrance. 

2. PDK Access Control Integration 

The FelixGate integration is enabled within the customer's PDK environment, allowing FelixGate to receive access history events relating to the configured entry point. 

When an access event occurs at the relevant door, PDK provides the access history event to FelixGate via webhook. FelixGate then uses this information alongside its own door activity data to identify legitimate entries and potential tailgating or unusual-entry events. 

Customer Requirements 

• An active PDK access control system. 
• A supported PDK-controlled entry point. 
• FelixGate tailgating detection hardware installed at the relevant entrance. 
• Access to their PDK system to enable the FelixGate integration. 

Integration Setup 

Once the FelixGate hardware has been installed: 

1. Log in. Log in to the relevant PDK system. 
2. Enable the integration. Enable the FelixGate integration within PDK. 
3. Obtain the System ID. Obtain the PDK System ID for the site. 
4. Provide the System ID. Send the System ID to FelixGate. 
5. Associate the facility. FelixGate associates the PDK system with the corresponding FelixGate facility. 
6. Map the door. FelixGate configures the relevant PDK door entry point against the FelixGate door. 
7. Test the integration. FelixGate confirms that access history events are being received correctly. 

Activation: Once testing has been completed successfully, the integration will be activated for the facility.

Data Received from PDK 

FelixGate receives access history information required to correlate access-control activity with physical entry activity at the door. 

This information is used solely for the operation of the FelixGate service, including determining whether an entry was associated with a valid access-control event. 

FelixGate does not require access to administer the customer's PDK system or modify users, credentials, schedules, access levels, or door configuration. 

Webhook Communication 

Access history information is provided from PDK to FelixGate using webhook events. This allows FelixGate to receive access events as they occur rather than periodically polling the PDK system. 

The webhook data is associated with the relevant PDK System ID and door entry point before being processed by FelixGate. 

Door Mapping 

Each FelixGate installation must be associated with the corresponding PDK door entry point. 

For sites with multiple controlled doors, FelixGate will confirm which PDK door or doors correspond to each FelixGate hardware installation. Only access events from the configured entry points are required for FelixGate tailgating detection. 

FelixGate Functionality 

The PDK integration provides access-control context to FelixGate but does not replace or alter the operation of PDK. PDK remains responsible for controlling access to the facility. 

FelixGate uses PDK access events in combination with FelixGate hardware and analytics to provide functionality including: 

• Tailgating detection. 
• Identification of entries where no corresponding access event is received. 
• Video evidence associated with door activity. 
• Access-event correlation within FelixGate reporting. 
• Facility entry and activity reporting.

Security and Access 

The customer remains responsible for their PDK system and access-control configuration. 

FelixGate only receives the information required to provide the FelixGate service and does not require customer administrator credentials to be shared with FelixGate. 

The PDK System ID supplied during onboarding is used to identify and associate the customer's PDK environment with their FelixGate facility. 

Support 

If access events are not appearing within FelixGate, FelixGate support may request confirmation of: 

• The PDK System ID. 
• The relevant PDK door name or entry point. 
• Whether the FelixGate integration remains enabled within PDK. 
• The approximate date and time of a recent test access event. 

FelixGate can then confirm whether the corresponding webhook event has been received and processed. 

Integration assistance 

onboarding@felixgate.com | www.felixgate.com