Skip to main content

Set up Paxton Net2 access control

Connect your Paxton Net2 server to Sign In App so your team can issue and return physical access credentials for visitors from Portal 2.0, and optionally sign people in when they tap a reader.

Before you start

Your Net2 version. Sign In App has two Paxton providers. Choose the one that matches your server.

Provider in Sign In App

Net2 versions

Paxton Net2 (v6.7 SR3 and later)

v6.7 SR3 and later

Paxton Net2 (v6.05 SR2 to v6.6)

v6.05 SR2 to v6.6

Versions below v6.05 SR2, and v6.7 up to v6.7 SR2, are not supported. To find your version, open Net2 on the server and go to Help > About Net2. The service release matters, so check the full build number.

On your Net2 server

  • The Net2 Local API is switched on, running and licensed. Your Account Manager can provide the Sign In Solutions licence file. See Troubleshoot the Paxton Net2 connection for how to check this on each version.

  • A Net2 operator for the integration with System engineer or Supervisor rights. We recommend a dedicated operator. Token Administrator and custom roles with reduced rights will not work.

  • A choice of tunnel or direct access (see below). Tunnel is the default and suits most sites.

In Sign In App

  • Admin access to Portal 2.0, with the Create/edit provider permission under Roles and permissions.

  • Education customers: on-premise access control is included in the Pro Education Bundle. If you are on Core, Enhanced, or the standard Education Bundle, upgrading to Pro Education adds this alongside Central Record, MIS integration, and SSO. Get in touch with your account manager to walk through what that setup looks like at your school.

Sharing this with your IT or security team? See Paxton Net2: what Sign In App reads, changes and stores.

Tunnel or direct access?

Tunnel access (recommended)

Direct access

How it works

A small Windows service (SIS Connector) runs on your Net2 server and makes an outbound connection to Sign In App

Sign In App connects to your server's public address

What you need

Permission to install the connector on the Net2 server

A public IP address or hostname for the server, with the Local API port reachable from the internet

Firewall changes

None. No inbound ports are opened

Inbound access to the Local API port

Server URL

Generated for you

You enter it, including the port if the Local API is not on the default


Step 1: Add the provider

Go to Manage > On-Premise Access Control. This page lists any providers you have already set up.

Select Add provider, then choose Paxton. The setup dialog shows which Net2 versions the provider supports.

Step 2: Setup provider

Enter a Server name. This is how the connection appears in Sign In App, so use something your team will recognise.

Choose Tunnel access or Direct access.

Tunnel access

  1. Select Download tunnel. Sign In App generates the server URL for you.

  2. Copy the downloaded file to your Net2 server and unzip it.

  3. Run the install file as an administrator. It installs the SIS Connector service and links it to this site.

  4. Back in Sign In App, select Next.

If Sign In App cannot reach your server through the tunnel yet, you will be asked to run the installer and try again. See Troubleshoot the Paxton Net2 connection if it still does not connect.

Direct access

  1. Enter the Server URL. This is your server's public IP address or hostname. Include the port if your Local API is not on the default port. Net2 v6.7 SR3 and later use HTTPS on port 8443. Net2 v6.05 SR2 to v6.6 use HTTP on port 8080.

  2. Select Test. You should see "Connection successful".

  3. Select Next.

Step 3: Authenticate user

Enter the details of the Net2 operator you created for the integration.

  • Username: the operator's name exactly as it appears in Net2, in the form "First name Last name".

  • Password: the operator's password.

Select Save. Sign In App connects to Net2 and pulls through your access levels and token types. If the connection succeeds but the sync fails, open the provider and select Refresh provider to try again.


After setup

Your Paxton server now appears on the On-Premise Access Control page. Open it to see three tabs:

  • Settings: the server name, URL and operator details, your connected sites, and preferences including Tap to sign in and out.

  • Access rules: which Net2 access levels each of your users is allowed to hand out.

  • Credentials: the cards and tokens you can assign to visitors.

Next, connect the sites this server covers and configure access rules and credentials.

You can read more about using access control here.


Good to know

  • Access starts when the credential is assigned, not at a pre-registration start time. Net2 does not support a start time on temporary access.

  • Card numbers are required for standard credential types. Facility codes are not used by Net2.

  • Visitor email addresses are written to Net2 custom field 9, the Net2 convention for email. Addresses longer than 50 characters may not match an existing Net2 user, which can create a second record.

  • Your existing door permissions are never changed. Visitors are granted temporary access only.

  • To change the operator or server URL later, open the provider's Settings tab. Some details are locked while credentials or cardholders exist on the connection.


We hope you've found this guide useful! For further information about the connection with Paxton Net2, please see the following guides:

Did this answer your question?