Organize access around the people and responsibilities already represented in GEM.
Physical access & visitors
Give the right people the right access.
GEM connects supported keypads, card readers, intercoms, locks, and gates with the people, schedules, and workflows that govern entry.
Access rules
A credential can do more than open a door.
With integrations that delegate credential decisions to GEM, a reported PIN or RFID event is matched to the applicable people, rules, and operating schedule.
A successful rule can unlock a connected door, open a gate, run a coordinated arrival macro, or simply record the event.
- 01PresentEnter a PIN or present a card or fob.
- 02EvaluateCheck the person, rule, schedule, and exceptions.
- 03ActSend a command, run a macro, or log only.
- 04RecordPreserve the result, reason, location, and action.
People and schedules
Access that follows the work.
Authorize individuals, reusable access groups, or anyone assigned a selected GEM role, then apply the days, hours, and exceptions that fit each entrance.
Keep resident, staff, service, and after-hours access on the schedule appropriate to each rule.
Apply holidays, shutdowns, and other date ranges consistently across multiple entrances.
Visitor management
Temporary should mean temporary.
Issue a time-limited PIN, assign only the access groups the visitor needs, and add a host, photo, or printed badge when the property calls for them.
Issue
Create a unique six-digit PIN for an hour, a day, a week, or a specific window.
Scope
Limit the visitor to the entrances represented by selected access groups.
Share
Deliver the code through the chosen process or print a visitor badge.
Expire or revoke
End access on schedule or stop it immediately without deleting the audit record.
The visitor PIN is displayed once when issued and stored encrypted afterward. At expiration or revocation, supported access hardware receives the updated credential state through its GEM driver.
Doorway events
More than credential entry.
GEM can bring entry, exit, visitor calls, and the record behind them into one access workflow.
Request to exit
A supported button or sensor can run a credential-free exit action and record the event.
Call buttons
A supported intercom or doorbell can log a visitor press, capture a snapshot when configured, and run a chime, notification, or video-preview workflow.
Audit and reports
Review who, when, where, result, reason, and action, then filter activity by person, entrance, or time period.
Credential, relay, REX, call-button, snapshot, synchronization, and offline-schedule capabilities vary by access device and GEM driver.
Exceptional conditions
Define the response before it is needed.
Build deliberate workflows for unusual conditions without asking the software to stand in for the physical access and life-safety design.
GEM’s lockdown state restricts ordinary rules to those explicitly permitted. Request-to-exit rules are allowed by default in GEM, while compliant egress must still be provided and validated by the property’s physical access design.
A separate per-user PIN can perform the expected entry action while silently running a configured macro and recording a duress event. It performs only the response designed for the project; GEM is not itself a monitored emergency-response service.
With an appropriate contact sensor, GEM can measure a held-open condition. An opening without a recent authorized unlock is logged as a possible unauthorized opening—not asserted as proof of forced entry.
Access rules, groups, holiday calendars, visitors, and access logs and reports require the Access Control & Visitor Management feature module. Some integrations make the physical access decision themselves and send GEM the resulting event; others support credential, schedule, and door-action synchronization.
Make entry easier to manage.
Bring the entrances, people, schedules, and supported hardware. We’ll show how GEM can turn them into a clear access and visitor workflow.