Genetec access control integration

Prerequisites

  • Before establishing a connection with Robin, please contact your Genetec representative to purchase the Robin part number GSC-1SDK-ROBIN-Platform. Purchasing the part number will allow Robin to communicate with Genetec WebSDK and ingest access control data.
  • This integration requires a Genetec username, password, and a Genetec WebAPI URL.

Overview

Integrate Genetec with Robin to enable Genetec-controlled doors to automatically check users into Robin with a badge swipe. This guide will walk you through the steps to set up and start using the integration. 

How it works

When users swipe their badges at the Genetec-controlled doors, they'll be automatically checked into the office via Robin, streamlining the check-in process and enriching attendance and usage analytics.

  • If a user has a desk reservation, they’ll be checked into their desk and reflected as "Checked in or confirmed on-site".
  • If a user does not have a desk reservation when they swipe their badge, a visit will be created, checked in, and reflected as "Confirmed on-site".
  • Admins can view a real-time list of who is in the office from the Daily Roster and see who checked in via a badge swipe. 
  • Badge data shows up in analytics as a desk check-in and/or counts towards someone "confirmed on site" and specifies the check-in method used. 

Genetec API Setup

  1. Navigate to System -> General Settings -> Roles.
  2. If you do not see a Web-based SDK in the roles list, a new connection is required. If it exists, skip steps 3 and 4. 
    • image.png
  3. Select Add an entity -> Web-based SDK > Properties
    • For this integration, we’re interested in the Port and Base URI.
    • The "Use of an SSL connection" setting should be off.
  4. Follow the installation steps. 
  5. Expose the WebSDK port by navigating to Windows Defender Firewall with Advanced Security > Inbound Rules. 
  6. Select New Rule -> Port -> TCP -> Specified Local Ports.
  7. Insert the set port value from the Genetec WebSDK properties page.
  8. Allow the connection.
  9. Enter the name of your inbound rule and then finish the setup.
  10. The new rule should appear in the Inbound Rules list. 
  11. Robin will require a username and password to successfully connect to the Genetec WebSDK. We recommend creating a new user who has permission to log in using the SDK.

Robin set up

  1. In the web dashboard, navigate to Manage > Integrations on the left.
  2. Scroll down to the "Access Control" section on the Integrations page.
  3. Locate Genetec and click Connect to begin the setup process.
  4. Select Connect account under the authentication section.
  5.  Enter your Genetec credentials and Genetec API URL. 
    • Genetec API URL is comprised of: (Note: Port and BaseURI information can be found on the Genetec WebSDK properties page)
      • A public IP address of your main Genetec server
      • WebSDK exposed port
      • WebSDK BaseURI
  6.  Select Authenticate. 
  7. After successfully connecting your Genetec account, you'll see a table mapping Genetec Door IDs to the designated buildings and floors.
  8. Use the table to configure the relevant buildings, doors, and floors where you want to enable automatic check-ins via Genetec.

Badge data handling

Robin pulls API payloads from the badging system containing event data. Records are processed, where all data except the email address, timestamp, and door ID is discarded before further processing.

Robin consumes 3 API calls per badge swipe event. Ensure your API call limits and quotas accommodate your expected usage.

Articles in this section

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