Connect your Genetec Security Center server to Sign In App so your team can issue and return physical access credentials for visitors from Portal 2.0.
Before you start
On your Genetec server
The Security Center Web SDK role is installed, licensed and running. Sign In App connects through the Web SDK, so it must be reachable from the machine running the tunnel, or from the internet for direct access.
The Sign In Solutions application ID is registered on your Web SDK role. Contact our support team for the ID if your Genetec administrator does not have it.
A Security Center user for the integration, with rights to view and manage cardholders, credentials and cardholder groups in the partition you will use. This is typically an administrator account. If you are unsure, check with your IT team.
The name of the partition that contains the doors visitors will use. If you only have one partition, it is selected for you.
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 Genetec server and makes an outbound connection to Sign In App | Sign In App connects to your Web SDK's public address |
What you need | Permission to install the connector on the server | A public IP address or hostname, with the Web SDK port reachable from the internet |
Firewall changes | None. No inbound ports are opened | Inbound access to the Web SDK 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 Genetec.
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 the server that runs your Web SDK role 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 Web SDK, including the port.
Select Test. You should see "Connection successful".
Select Next.
Step 3: Authenticate user
Enter the Username and Password of the Security Center user you created for the integration, then select Next.
Step 4: Configure partitions
Partitions control which doors are visible at your location. Select the partition that contains the doors you want to use for visitor access. If you only have one partition, it is selected by default.
Select Save. Sign In App connects to Security Center and pulls through your cardholder groups and credential formats. If the connection succeeds but the sync fails, open the provider and select Refresh provider to try again.
After setup
Your Genetec 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.
Access rules: which Security Center cardholder groups each of your users is allowed to hand out.
Credentials: the cards 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
Tap to sign in and out is not yet available for Genetec.
Visitors are created as Security Center visitors with temporary group membership. Your existing cardholders and permissions are never changed.
The username and partition are locked once credentials or cardholders exist on the connection. To change them, return all credentials first.





