<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=7847562&amp;fmt=gif">
Home > Integrations

Identity-driven key management for iLOQ

Key2XS connects the iLOQ digital locking system to your identity and access management platform. The identities, roles and policies you govern in your IAM are translated into iLOQ key rights automatically, so who can open which lock is always a direct reflection of who someone is and what their role allows.

Request a demo

Why organizations choose iLOQ, and what remains

iLOQ built its reputation on removing the classic weaknesses of electronic locking: its self-powered digital locks need no batteries in the cylinder and no wiring to the door. That makes iLOQ a natural fit for exactly the places where access is hardest to manage: dispersed sites, unmanned locations, pumping stations, distribution facilities and technical spaces spread across a region.

The locking technology solves how access is enforced. What remains is governing who should have that access in the first place. Those decisions live in your IAM system, in roles, contracts, approvals and lifecycle events. Without a connection between the two worlds, the iLOQ administration is maintained by hand:

Key2XS closes that loop. Your IAM decides, iLOQ enforces, and Key2XS keeps the two synchronized in near real-time, with a tamper-evident audit trail linking every key right to an identity and a policy decision.

How the integration works

  1. Connect. Key2XS connects to your iLOQ environment and your IAM system through their standard interfaces. A standard integration is live in under two hours, with no custom development. Your locking plan, locks and keys remain exactly as they are.
  2. Map. Roles and groups in your IAM are mapped to iLOQ key rights and lock groups. A role like “Service Engineer - Water Production” can correspond to precisely the pumping stations, treatment facilities and technical rooms that role requires.
  3. Orchestrate. Lifecycle events in the IAM, such as onboarding, role changes, contract expiry and offboarding, are applied to iLOQ key rights in near real-time. Revoking an identity withdraws its physical access in the same movement.
  4. Prove. Every key right traces back to who approved it, under which role, and when. Compliance questions about physical access are answered in minutes instead of days.

Works with the IAM system you already run

Key2XS provides pre-built connectivity for the identity platforms most organizations already operate:

The same platform also governs the ASSA ABLOY CLIQ ecosystem, so organizations running iLOQ at one site and eCLIQ or PROTEC2 CLIQ at another manage both from a single identity-driven flow.

Built for critical environments

iLOQ estates are typically found where continuity and safety are non-negotiable: utilities, telecom, transport, government, healthcare and industry. Key2XS is built for exactly those environments.

Frequently asked questions

Identity-driven key management for iLOQ, answered.

See your IAM and iLOQ working together

Get a guided walkthrough of how identity, policy and iLOQ keys come together in one auditable flow.