Genea access control

Overview

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

Note

The Genea integration requires obtaining an API key for your Genea account and having Genea Access (cloud). Please contact your Genea representative to obtain your API key.

How it works 

When users swipe their badges at the Genea-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. 

How to set it 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 Genea and click Connect to begin the setup process.  
  4. Click Connect account under the authentication section.  
  5. Enter your public Genea API key. Contact your Genea representative if you don't have a public API key. 
  6. After successfully connecting your Genea account, you'll see a table mapping Genea Door IDs to the designated buildings and floors. 
  7. Use the table to configure the relevant buildings, doors, and floors where you want to enable automatic check-ins via Genea. 
    • Screenshot 2025-01-16 at 22.00.20.png
  8. Click Save. 
  9. Review and confirm your changes and click Save.  Screenshot 2025-01-16 at 22.00.42.png

Badge data handling

Robin receives API payloads from the badging system containing event data. The payload reaches Robin's edge, where all data except the email address, timestamp, and door ID is discarded before further processing.

 

Articles in this section

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