Overview
The Atrium + Genea Integration allows Genea to pull identity, credential, and access-related data directly from Atrium. Atrium acts as the system of record for users and credentials, while Genea consumes this data to provision users, and assign access within the Genea access control.
This integration enables campuses and enterprises to centralize user lifecycle management in Atrium while leveraging Genea for secure, cloud-based access control—reducing manual provisioning, minimizing errors, and ensuring real-time synchronization.
How the Integration Works
Atrium is the authoritative source for:
Users (students, staff, contractors, etc.)
Credential
User attributes
Genea periodically pulls data from Atrium using Atrium’s APIs.
Updates made in Atrium (new users, changes, deactivations) are reflected in Genea at an interval of 15 mins.
Important:
This is a one-way data flow from Atrium to Genea. Changes made in Genea do not sync back to Atrium.
To successfully complete this integration, it is imperative to have Global Admin privileges within the Genea platform.
Please request the Atrium team to enable the “Update Person Status” toggle in Atrium (Configuration → Cron Jobs → Update Person Status) to ensure Genea receives complete user lifecycle updates.
Entity Mapping: Genea and Atrium System
Outlined below is the entity mapping between Genea and the Atrium system.
Entity in Atrium Campus | Entity in Genea System |
People | User |
Campus ID | External ID |
Access Groups | User Groups |
ID Type | Card Type |
Get Ready to Activate the Genea + Atrium Integration
Before initiating the Genea + Atrium integration, follow these preparation steps:
Enable External ID:
If the External ID attribute is not enabled in your Genea web application, follow these steps to enable it:
Log in to the Genea Web Application.
Navigate to User Management > Attributes.
Turn on the toggle for External ID.
Installation Steps
Log in to the Genea web application.
Navigate to Integrations → Atrium Campus.
Enter the Atrium API details:
API Endpoint
Authentication credentials
User Group Mapping:
To ensure seamless integration between Genea and Atrium, Access Groups created in the Atrium system are automatically created as User Groups in Genea along with their memberships. If the Atrium integration is uninstalled in Genea, any User Groups that were created through the Atrium integration will also be deleted.
Activate Atrium Provisioning Integration on Genea Platform
Access the Integrations page within the Global Overview, locate Atrium, and initiate the integration by selecting 'Install'.
Provide the Atrium API Endpoint and credential details and click Install. Genea will utilize this primary connection to establish a link with the Atrium system, allowing Genea to pull the users and credentials.
If you do not possess an Atrium API Endpoint and credentials, kindly reach out to the Atrium team for assistance in obtaining it. Upon successful connection establishment, you will be automatically redirected to the Atrium Integration Details page.
Genea will only encounter difficulties connecting with the Atrium system if the API Endpoint is inaccurate or if the Password has been modified in Atrium. To re-establish the connection, simply edit the Atrium Configurations by clicking on 'Edit.'
How Genea Retrieves User Data from Atrium
Genea periodically pulls data from Atrium using Atrium’s APIs. Updates made in Atrium (new users, changes, deactivations) are reflected in Genea at an interval of 15 mins. Admin can pull events manually by using 'Sync Now' option.
Validate the successful processing of events by Genea. Go to the Sync Logs tab and utilize the available filters to see the events. In the event of unsuccessful or failed processing, click on 'View Details' to access the specific reasons behind it.
Card Types
The Card Types section defines which card types from Atrium will get synced in Genea. If no card type has been selected, cards will not get synced from Atrium to Genea.
You can select a different card format for each unique card type. This is particularly useful for Assa locks, as card format is mandatory for Assa locks.
If the credential (card number) in Atrium includes a facility code prefix, enable the Strip Facility Code option to remove the prefix before processing the card number.
For example, if the credential number in Atrium is 9011000014, where 901 is the facility code and the actual card number is 1000014, enter 901 in the Facility Code field and select the Strip Facility Code checkbox.
Support
For assistance:
Contact Atrium Support for API or data configuration issues.
Contact Genea Support for sync behavior, access rules, or Genea platform questions.