Paxton access control explained for security teams and installers

a[data-rs-seo-link]{text-decoration:underline!important;color:#1a56db!important;cursor:pointer!important;}a[data-rs-seo-link]{text-decoration:underline!important;color:#1a56db!important;cursor:pointer!important;}

What Paxton access control means in practical terms

Paxton access control is best viewed as a product family, not as one door controller. The range includes offline standalone systems for simple doors, Net2 for centrally managed networked access control, and Paxton10 for web-based access control with integrated video management. The right choice depends on how the building will be administered, how many doors and users are involved, whether video must be tied to access events, and how much remote management the security team needs. For a broader primer on electronic door security, see the Access Control section.

The planning issue is that Paxton systems can serve very different sites. A small office may only need card or PIN control at a few independent doors. A school, warehouse, clinic, or multi-tenant commercial building may need central user administration, event reporting, lockdown functions, and integration with alarms or video. A distributed organization may put more weight on browser access, mobile credentials, and multi-site management. Those requirements point to different Paxton platforms.

The main Paxton system choices

Paxton’s public product literature groups its access control offer around several system types. For most specification discussions, three choices matter most: standalone access control, Net2, and Paxton10. Door entry and wireless locksets may also be part of the design, but they should be treated as supporting subsystems rather than substitutes for a complete access control strategy.

Standalone access control is straightforward, but it comes with an operational tradeoff. If a token is lost or a code must be changed, the update generally has to be handled at the door. That may be acceptable for a storage room or a small premises, but it becomes inefficient when staff turnover, temporary visitors, or multiple departments are involved.

Net2 is Paxton’s established networked access control system. Paxton states that Net2 software can organize and report on up to 50,000 users and 1,000 doors. Net2 Lite covers standard access privileges and reporting, while Net2 Pro adds advanced functions such as security lockdown, anti-passback, fire alarm and multi-zone intruder alarm integration, card designer, timesheet, and timeline features. This makes Net2 a practical fit where access control is the primary requirement and administrators are comfortable with a PC-based management model.

Paxton10 is positioned differently. Paxton describes it as a web-based system that combines access control and video management. Current Paxton10 literature lists capacity for up to 100 sites on a single system, up to 1,000 doors, up to 1,000 cameras, and up to 50,000 users. It also supports browser administration, mobile apps, Bluetooth smart credentials, site plans, dashboards, reporting, and event handling. For security teams that want video verification connected to access events, Paxton10 can reduce the need to manage separate access and video interfaces.

Net2 and Paxton10 compared

The most common Paxton specification decision is not always Paxton versus another brand. It is often Net2 versus Paxton10. The difference is not simply old versus new. Net2 remains relevant where the priority is mature networked access control, a PC administration workflow, and compatibility with existing Net2 infrastructure. Paxton10 is more appropriate where the project brief calls for a browser-based interface, integrated video management, Bluetooth smart credentials, and remote multi-site administration.

A useful starting point is the operating model. If the building already has trained staff, installed Net2 hardware, and a defined PC-based workflow, replacing it only for novelty may not deliver value. If the project is new, requires video alongside access control, or covers multiple sites where administrators need browser and mobile access, Paxton10 deserves closer review.

There is also a procurement distinction. Product names alone do not define the complete system. Controllers, readers, credentials, power supplies, locks, fire interfaces, network design, and software edition all affect the final result. A written specification should state the required functions, not just the platform name.

Architecture and components that affect reliability

A Paxton access control system is built from several layers. At the door, a controller manages connected devices such as readers, keypads, electric locks, request-to-exit devices, and door contacts. Paxton’s controller literature emphasizes that placing the controller in a secure area helps protect lock control from direct interference at the reader side. This is a basic but important design principle for any electronic access control system.

Credentials are another layer. Cards, fobs, PINs, and mobile credentials all identify a user, but they carry different risk and management profiles. Cards and fobs are familiar and easy to issue. PINs are inexpensive but can be shared. Mobile credentials can reduce physical token handling, but they introduce device management, user support, and policy questions. For example, a facility should decide what happens when an employee changes phones, loses a smartwatch, or leaves the organization.

Software is the management layer. It determines who can enter, when access is allowed, what events are logged, which administrators can make changes, and how reports are generated. For regulated or higher-risk environments, administrator permissions and audit trails should be treated as security controls, not just convenience features.

Network design is often the hidden layer. Net2 and Paxton10 both depend on reliable connectivity for administration and reporting, even though door controllers may have local intelligence for day-to-day decisions. Segmentation, backups, documented IP addressing, firmware and software update procedures, and secure remote access should be agreed before commissioning. These details are not always visible to end users, but they determine how well the system can be supported over time.

Current Paxton10 developments to note

Paxton10 has received notable feature updates in recent product literature. Paxton lists Paxton10 I/O Connectors as available to buy from May 18, 2026. The connectors are designed to add inputs and outputs that work with triggers and actions, allowing the system to respond automatically to events such as a token presentation, a door opening, or an access decision. Paxton describes examples including connected lighting, heating, air conditioning, water, lifts, and alarms.

Paxton also identifies several Paxton10 software additions by version. Improved multi time zone management is listed for Paxton10 v4.9 SR6, which matters for multi-site systems where events and reports must reflect each site’s local time. Encrypted credentials are listed for Paxton10 v4.9 SR1, with the aim of improving resistance to unauthorized duplication of cards and tokens. Lockdown and email notifications are listed for Paxton10 v4.7 SR7, giving administrators more options during emergencies and for real-time visibility of system activity. See also: Alarm and Detection.

These updates do not automatically mean every installed Paxton10 system has every feature. Version, region, hardware generation, credential type, and commissioning choices can all matter. When a specification requires encrypted credentials, smartwatch access, remote reboot, I/O automation, or time zone reporting, those features should be verified against the exact product versions being supplied.

Security and compliance considerations before specifying

Access control is both a physical security system and an IT-connected system. It should therefore be reviewed by facilities, security, and IT stakeholders. The physical side asks whether the correct doors are controlled, whether locks fail safe or fail secure as required, whether fire egress is protected, and whether door hardware complies with local code. The IT side asks how software is updated, how remote access is secured, where backups are stored, and who has administrator privileges.

Credential security deserves specific attention. The security industry has moved steadily toward stronger reader-to-controller communication and better credential protection. The Security Industry Association’s Open Supervised Device Protocol, commonly called OSDP, is widely discussed in the sector as a more capable alternative to legacy Wiegand because it supports bidirectional communication and secure channel options. If a project has a formal requirement for OSDP Secure Channel, encrypted credentials, or a specific government identity standard, the designer should confirm exact support at the model and configuration level rather than assuming brand-level compatibility.

For higher-risk sites, anti-passback, lockdown, muster or roll call reporting, door forced alarms, door held open alarms, and integration with intruder or fire alarm systems may be essential. These features may depend on software edition, platform, and correct field wiring. They should be listed in the scope of work and tested during handover.

A practical planning checklist

Before choosing a Paxton platform, document the operating requirements in plain language. The following checklist helps avoid under-specified systems:

• Count controlled doors, monitored doors, readers, request-to-exit devices, and door contacts separately.
• Estimate active users, temporary users, contractors, and expected growth over three to five years.
• Define administrator roles, including who can add users, change schedules, run reports, and trigger lockdown.
• Decide whether access events need linked video evidence in the same interface.
• Confirm whether the site needs mobile credentials, physical cards, fobs, PINs, or a mixture.
• List integrations, including fire alarms, intruder alarms, elevators, video systems, visitor management, and HR databases.
• Ask how backups, software updates, and remote support will be handled.
• Require a handover package with as-built drawings, device schedules, administrator procedures, and test records.

The best specification is not necessarily the longest one. It is the one that makes responsibilities clear. For example, “Paxton10 with video” is less useful than “control 24 doors, link lobby and loading dock access events to recorded video, support remote administration for two sites, and provide role-based administrator permissions.”

Frequently asked questions

Is Paxton access control suitable for small businesses?

Yes, but the platform should match the scale. A very small site may use standalone access control if it does not need central reporting. A growing business with multiple doors and staff turnover will usually benefit from Net2 or Paxton10 because users and permissions can be managed centrally.

Is Net2 being replaced by Paxton10?

Paxton’s public materials continue to present Net2 and Paxton10 as separate solutions. Net2 remains the networked access control option, while Paxton10 is positioned around web-based management and integrated video. Existing Net2 sites should evaluate business need rather than assume an automatic migration path.

Can Paxton access control use mobile credentials?

Paxton10 supports Bluetooth smart credentials through the Paxton Key app on compatible systems. Net2 mobile and remote functions depend on the software edition, hardware, and supported Paxton services in use. The safest approach is to verify mobile credential requirements before selecting readers and controllers.

What is the biggest mistake when planning a Paxton system?

The biggest mistake is specifying a product name without defining the operating requirements. Door count, user count, video needs, credential policy, emergency lockdown, integrations, reporting, and administrator permissions should be documented before hardware is ordered.

Should access control be handled by facilities or IT?

Both should be involved. Facilities typically understand doors, locks, egress, and daily building operations. IT understands networks, remote access, backups, and account security. Modern access control touches both domains, so shared ownership usually produces a more reliable system.