RFID card reader
For the selected card or fob technology at a controlled entrance.
Review card-reader detailsAccess control
Access control systems for buildings and sites.
Connect doors, readers, credentials, visitors and vehicle access to one operational record in Lexoh Security Center.
01
Credentials and readers
02
Visitor access
03
Schedules and permissions
04
Remote controls
05
Events and audit
One operating environment
What is an access control system and what does it manage?
An access control system checks who may enter, where and when, then directs the connected door or barrier. For a commercial building or site, it connects credentials, readers, controllers and doors or barriers so authorized people and vehicles reach the right zone at the right time, with access events available for review. Lexoh brings credentials, permissions, equipment and access events into Security Center according to the site’s configuration.
Access workflow
How does access control work at an entrance?
View full size ↗ Security Center
Manage sites and devices from one operational map.
See site status, connected equipment and recent activity in the same interface used to manage the access system.
- Site and device visibility
- Access activity in context
- Remote actions from authorized workflows
View full size ↗ Visitors and contractors
How do you manage visitor and contractor access?
Define the permitted zones and times for visitors and contractors. Authorized staff can update or deactivate credentials as the visit changes, according to the configured workflow.
- Visitor and contractor records
- Time and zone permissions
- Updates by authorized staff
Physical and digital
Which equipment belongs at the entrance?
Readers, kiosks and barriers are selected around the real entrance. Lexoh then connects the device, the person or vehicle, and the resulting event.
- QR, RFID and NFC workflows
- Connected lane and door equipment
- One record for access and operations
Site planning and modernization
What should you check before upgrading access control?
Start with the entrances, existing controllers, readers, locks or barriers, power and network. Document who administers access and how each entrance must behave during an interruption before choosing the final configuration.
- Equipment and credential compatibility
- Roles, support and maintenance responsibilities
- Documented interruption and recovery procedures
Reader selection
What must match between the credential, reader and controller?
Use the catalogue to identify the hardware category, then confirm the exact credential and controller combination. Record the supporting document or test result beside each selection.
QR scanner
For supported code presentation in the configured access workflow.
Review QR-scanner details
UHF vehicle reader
For the selected vehicle tag and a confirmed reading zone.
Review UHF-reader details| Decision to document | RFID card reader | QR scanner | UHF vehicle reader |
|---|---|---|---|
| Credential evidence | Confirm the exact card technology and format; matching frequency alone is insufficient. | Confirm the supported code type and the system that issues or validates the credential. | Confirm tag and reader regional band, mounting and the intended vehicle assignment. |
| Controller connection | Record reader model, interface and the approved controller configuration. | Record the scanner interface and where expiry or reuse rules are applied. | Record the reader interface and how identification reaches the access decision. |
| Site acceptance | Test authorized, revoked and incompatible sample credentials at the selected opening. | Test the intended phone or printed presentation and the agreed rejected-code response. | Test the intended lane and adjacent-lane conditions using the actual vehicle and tag setup. |
The project record should state the models, versions, evidence reference and reviewer. Leave a combination unresolved until the selected arrangement is confirmed.
Connected equipment
Build the access point around the site.
Choose the reader, assistance and lane equipment required by the entrance, then manage it through the same platform.
QR scanners
Configured code-based access at the point of entry.
View scanner
RFID card readers
Credential reading for configured access workflows.
View reader
IP intercom
A direct assistance path at the entrance.
View intercom
Lane barriers
Physical lane response connected to the access decision.
View barriers
Documented installation
Designed around the entrance that already exists.
This Collège Sainte-Anne lane combines the user interface, credential readers and automatic barrier in one clear passage.
See the Collège Sainte-Anne installationAccess-control questions
The essentials for planning a connected entrance.
Match the access method to the people, vehicles and entrances being managed. QR, RFID and NFC workflows use the readers selected for the project. Confirm credential compatibility, equipment interfaces and permission rules before choosing the final configuration.
When the configured workflow supports it, credentials can be limited to the zones and times required for a visit. Authorized staff can update or deactivate access as the visit changes. Define the visitor groups, approval responsibilities and access periods before configuration.
Yes. When included in the deployed architecture, Lexoh Security Center brings access events, connected devices, users and site context into one operational interface. Available records and actions depend on the configured equipment and permissions.
Yes. A project can connect the user interface, credential reader, assistance equipment and barrier so they operate as one configured entrance.
Begin with an inventory of the controllers, readers, credentials, locks or barriers, cabling, power and network. Equipment can be retained only when its condition and documented interfaces fit the proposed architecture. Confirm the migration stages, operating responsibilities and acceptance tests before installation.
The answer depends on the selected controllers, stored configuration, connected equipment and available power. The project must document the required local access behaviour, event handling and recovery process. Test those conditions during commissioning; cloud management alone does not define how an entrance behaves during an outage.
Compare who administers credentials, maintains software and equipment, manages connectivity and backups, and handles support and recovery. Document data access, retention and integration responsibilities for the proposed system. Use the same entrances, credentials and service scope when comparing proposals.
First identify the person and the missing credential. An authorized operator should deactivate that credential according to the site’s process, then arrange a replacement with the appropriate permissions. Test the replacement at the required entrances and check that the lost credential no longer grants access, without changing other users’ permissions.
Start with the entrance, approximate time and credential used. Compare the available access event with the person’s active permissions and the permitted zone and schedule, then check the connected device’s status. This helps distinguish a permission issue from an equipment or connection issue before the team chooses an authorized response.
A standalone keypad typically has permissions administered at the device, while centrally managed access uses a management system to administer the connected entrances. Compare who changes permissions, how changes reach each opening and what event records are available in the selected products. This is a different decision from cloud versus on-premise hosting; neither label alone proves a particular feature or security outcome.
A useful quote starts with the entrances, people and vehicles to manage, the zones and schedules they need, and the access methods they will use. Include existing readers, controllers, doors or barriers, power, network, site conditions, outage expectations, installation responsibilities and ongoing support so the proposal describes the complete operating scope.
A multi-site deployment can be organized in one operating environment when the selected platform, communications, equipment interfaces and permissions support it. Confirm which users, credentials, schedules and reports are shared, which remain site-specific, and how each location is expected to operate during a connection or power interruption.
Plan the complete entrance
Bring the field equipment and the operating view together.
Tell us about the people, vehicles, entrances and rules your site needs to manage.