Connect your Lenel OnGuard 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
On your OnGuard server
OpenAccess is installed, licensed and running. Sign In App connects through the OpenAccess API.
An OnGuard user for the integration, with rights to manage cardholders, badges and access levels in the segment you will use. This is typically an administrator account. If you are unsure, check with your IT team.
The directory that user signs in with (for example the internal OnGuard directory or your Active Directory).
The name of the segment that contains the doors visitors will use. If you only have one segment, it is selected for you.
For direct access only: OpenAccess uses HTTPS, so your server needs a hostname and a valid certificate that Sign In App can trust. Tunnel access avoids this.
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.
Tunnel or direct access?
| Tunnel access (recommended) | Direct access |
How it works | A small Windows service (SIS Connector) runs on your OnGuard server and makes an outbound connection to Sign In App | Sign In App connects to your OpenAccess address |
What you need | Permission to install the connector on the server | A public hostname with a valid HTTPS certificate, and the OpenAccess port reachable from the internet |
Firewall changes | None. No inbound ports are opened | Inbound access to the OpenAccess port |
Server URL | Generated for you | You enter it, including the port |
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 OnGuard.
Step 2: Setup provider
Enter a Server name. This is how the connection appears in Sign In App.
Choose Tunnel access or Direct access.
Tunnel access
Select Download tunnel. Sign In App generates the server URL for you.
Copy the downloaded file to your OnGuard server and unzip it.
Run the install file as an administrator. It installs the SIS Connector service and links it to this site.
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.
Direct access
Enter the Server URL of your OpenAccess service, including the port.
Select Test. You should see "Connection successful".
Select Next.
Step 3: Authenticate user
Enter the Username and Password of the OnGuard user you created for the integration.
Select the Directory that user belongs to. The list comes from your OnGuard server.
Select Next.
Step 4: Configure segments
Segments control which doors are visible at your location. Select the segment that contains the doors you want to use for visitor access. If you only have one segment, it is selected by default.
Select Save. Sign In App connects to OnGuard and pulls through your access levels and badge types. If the connection succeeds but the sync fails, open the provider and select Refresh provider to try again.
After setup
Your OnGuard server now appears on the On-Premise Access Control page. Open it to see three tabs:
Settings: the server name, URL and user details, your connected sites, and preferences including Tap to sign in and out.
Access rules: which OnGuard access levels each of your users is allowed to hand out.
Credentials: the badges 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.
Allow more than one badge per person
OnGuard limits how many active badges one cardholder can hold. If that limit is one, a visitor who already holds a credential cannot be given another. Sign In App refuses the assignment and asks you to return the existing credential first.
To allow more than one active badge per cardholder:
In OnGuard, open System Administration > Administration > Cardholder Options.
On the General Cardholder Options tab, set Maximum active badges per cardholder to a value greater than 1.
A value of 1 restricts each cardholder to a single active badge.
Good to know
Visitors are created as OnGuard cardholders in your chosen segment, with a badge and access level that expire when the visit ends. Your existing cardholders and access levels are never changed.
Credential expiry uses the timezone set on the connection (Settings tab, Preferences), not the timezone of the computer you are working on.





