Integrating Paxton Net2 with Custr Check-In

The Paxton Net2 integration allows organisations to use their existing Paxton access control system to automatically check staff in and out of Custr Check-In.

When a staff member uses their existing Paxton fob at a configured access point, Custr can automatically record their check-in or check-out without requiring a separate attendance process.

The integration is read-only from Paxton Net2. Custr does not write information back to Paxton, change access permissions or modify your existing access control configuration.

Before setting up the integration:

The initial Paxton connection is completed through:

Site → Integrations

Go to:

Site → Integrations

Select the Paxton integration.

Download the Custr Windows integration app from the Integrations page.

Install the application on the same Windows computer or server that is running Paxton Net2.

Open the Custr Windows app and follow the on-screen setup process.

The application will guide you through connecting:

Once the integration has been successfully connected, a new option will become available under:

Configuration → Paxton

This is where you manage the integration going forward.

If Configuration → Paxton is not visible, the Paxton integration has not yet been successfully set up.

The Custr Windows application acts as the connection between your local Paxton Net2 installation and the Custr cloud platform.

The process works as follows:

Paxton continues to manage physical access independently.

Custr does not:

Once connected, go to:

Configuration → Paxton

From here you can manage:

Custr needs to know which Paxton user corresponds to which Custr Employee.

Custr will suggest possible matches using information such as:

Review the suggested matches and confirm the correct Employee.

If the suggested match is incorrect, you can change it or search for the appropriate Custr Employee manually.

The integration does not automatically create Custr Employees from Paxton.

If someone exists in Paxton but is not yet present in Custr, add them as an Employee in Custr first and then complete the linking process.

Paxton Net2 organises its access points as Doors.

Each Door can have associated readers that detect staff fob activity. Custr uses these Paxton access events to determine whether an attendance action should take place.

Go to:

Configuration → Paxton → Doors

Each Door can be configured individually.

This allows you to decide which areas of your Paxton setup should affect Custr attendance without changing how those Doors operate within Paxton itself.

Activity at this Door can check an Employee into Custr.

For example:

Main Entrance → Check-In Only

When an Employee arrives and uses their Paxton fob, Custr records their check-in.

Activity at this Door can check an Employee out of Custr.

For example:

Main Exit → Check-Out Only

When an Employee leaves and uses their Paxton fob, Custr records their check-out.

Custr uses the Employee's current attendance status to determine the action.

This can be useful where the same access point is used when both arriving and leaving.

Activity at the Door does not trigger any Custr attendance action.

The Door and its associated readers continue to operate normally within Paxton.

These attendance options are applied within Custr only and do not change the Door's behaviour in Paxton Net2.

Each Door also has an Active toggle.

This allows you to enable or disable that Paxton Door for Custr attendance without making any change to the Paxton access control configuration.

Once Employees are linked and Doors are configured, staff do not need to follow any additional Custr process.

They simply use their existing Paxton fob as normal.

For example:

Paxton is shown as the Employee's check-in method.

The same process applies when an appropriate Paxton event triggers a check-out.

Custr currently includes a one-minute repeat protection period.

If the same Employee generates another qualifying Paxton event within one minute, the repeat event is ignored.

This helps prevent an accidental second event from immediately reversing or duplicating an attendance action.

The event remains visible within the Paxton audit information so administrators can see why no attendance change was made.

Go to:

Configuration → Paxton → Audit Log

The Paxton Audit Log provides visibility of recent integration activity for up to seven days.

This can include events such as:

Where an event does not result in an attendance change, the audit information can help explain why.

For example:

Paxton activity can also be viewed against an individual Employee.

Go to:

Directory → Employees

Select the Employee and open:

Paxton Audits

This provides a history of the Paxton events associated with that Employee.

Check the following areas.

Confirm that the Custr Windows application is running and connected to the correct Paxton Net2 installation and Custr site.

The Employee must:

Having a user in Paxton alone is not enough to create attendance activity in Custr.

Go to:

Configuration → Paxton → Doors

Confirm that the relevant Door is active.

Check the selected action.

For example, a Door configured as Check-In Only will not check an Employee out if they are already checked in.

If another event for the Employee occurred within the one-minute repeat period, Custr may intentionally ignore the second event.

Go to:

Configuration → Paxton → Audit Log

The Audit Log can be used to see whether Custr received the event and why an attendance action was or was not performed.

No. The integration is read-only. Custr reads the information and events required for attendance but does not write changes back to Paxton.

Yes. Staff continue using their existing Paxton fobs and access control process.

No. Employees must already exist within Custr before they can be linked to their Paxton user.

Yes.

Each Door can be configured independently as:

Yes. Configure the Door as Both.

Custr will then use the Employee's current attendance status to determine whether the event checks them in or out.

No. Paxton continues to manage physical access as normal.

Custr uses the relevant Paxton events for attendance without changing users, permissions, Doors or access behaviour within Net2.

Go to:

Configuration → Paxton → Audit Log

You can also view activity relating to an individual Employee through their Paxton Audits tab.

The Paxton Net2 integration allows staff to use their existing Paxton access control process while automatically updating their attendance within Custr Check-In.

The integration is initially set up through:

Site → Integrations

Once connected, it is managed through:

Configuration → Paxton

From there, administrators can:

The connection remains read-only, so your existing Paxton users, permissions, Doors and access control configuration remain managed entirely within Paxton.