Genetec access control integration

About the Genetec integration

Integrate Genetec with Robin so that a badge swipe at a Genetec-controlled door checks users into Robin automatically. This article shows how to set up and use the integration.

Prerequisites

  • Before you connect to Robin, contact your Genetec representative to buy the Robin part number GSC-1SDK-ROBIN-Platform. This part number lets Robin communicate with Genetec WebSDK and ingest access control data.
  • This integration requires a Genetec username, password and Genetec API URL.

How it works

When users swipe their badges at Genetec-controlled doors, Robin checks them into the office automatically. This makes check-in faster and adds data to attendance and usage analytics.

  • If a user has a desk reservation, Robin checks them into their desk and shows them as "Checked in or confirmed on-site".
  • If a user has no desk reservation when they swipe their badge, Robin creates a visit, checks it in and shows the user as "Confirmed on-site".
  • Admins see a real-time list of who is in the office on the Daily Roster, and see who checked in with a badge swipe.
  • Badge data shows in analytics as a desk check-in, as a count toward "confirmed on site", or both. It also shows the check-in method.

Set up the Genetec API

In Genetec, add a Web-based SDK role, open its port in the Windows firewall and create a user for Robin.

Add a Web-based SDK role

Add the role that lets Robin connect to Genetec.

  1. In Genetec, go to System > General Settings > Roles.
  2. Look for a Web-based SDK in the roles list. If it exists, skip to Expose the WebSDK port. If you do not see one, you need a new connection. Continue with the next step.
  3. Select Add an entity > Web-based SDK > Properties.
    • For this integration, you need the Port and Base URI. By default, the port is 4590 and the base URI is WebSdk.
    • Turn on the Use SSL connection setting. With it on, the WebSDK address uses https.
  4. Follow the installation steps.

Expose the WebSDK port

Open the WebSDK port in the Windows firewall so Robin can reach it.

  1. In Windows, go to Windows Defender Firewall with Advanced Security > Inbound Rules.
  2. Select New Rule > Port > TCP > Specified Local Ports.
  3. Enter the port value from the Genetec WebSDK properties page.
  4. Allow the connection.
  5. Enter a name for your inbound rule.
  6. Finish the setup. The new rule should appear in the Inbound Rules list, for example Allow TCP port 4590 inbound.

Create a user for Robin

Robin needs a username and password to connect to the Genetec WebSDK. Robin recommends that you create a new user who has the Log on using the SDK privilege.

Set up Robin

In Robin, connect your Genetec account and choose where badge swipes check people in.

  1. In the Robin web dashboard, go to Manage > Integrations.
  2. Under Add Connectors, search for Genetec. You can also select By category and find Genetec under Access Control.
  3. Select Set up next to Genetec. The Genetec integration page opens.
  4. In the Authentication section, select Connect account. The Connect Genetec account window opens.
  5. Enter your Genetec username, Genetec password and Genetec API URL. The Genetec API URL has these parts:

    • The public IP address of your main Genetec server
    • The WebSDK port that you exposed
    • The WebSDK base URI

    You find the Port and Base URI on the Genetec WebSDK properties page. With the default values and Use SSL connection on, the URL looks like https://<public IP address>:4590/WebSdk. If Use SSL connection is off, the URL starts with http://.

  6. Select Authenticate. When your Genetec account connects, you see a table that maps Genetec Door IDs to buildings and floors.
  7. In the table, configure the buildings, doors and floors where you want automatic check-ins through Genetec.

Badge data handling

Robin pulls API payloads with event data from the badging system. When Robin processes the records, it discards all data except the email address, timestamp and door ID before further processing.

Robin uses 3 API calls for each badge swipe event. Make sure your API call limits and quotas allow for your expected usage.

Articles in this section

Was this article helpful?
0 out of 0 found this helpful
Share