Does Key2XS support both eCLIQ and PROTEC2 CLIQ?

Yes. Both product lines run on ASSA ABLOY's CLIQ technology and are administered through the same management environment. Key2XS supports both, including estates that combine them.

Is ASSA ABLOY CLIQ the same as eCLIQ and PROTEC2 CLIQ?

CLIQ is the underlying ASSA ABLOY electronic key technology. eCLIQ and PROTEC2 CLIQ are the product lines built on it, and Key2XS works with the CLIQ ecosystem as a whole.

Is the Key2XS CLIQ integration certified by ASSA ABLOY?

Yes. The Key2XS integration is certified by ASSA ABLOY. On the identity side, Key2XS is also a certified SailPoint Technology Alliance Partner.

Which IAM systems can manage ASSA ABLOY CLIQ keys through Key2XS?

Key2XS provides pre-built connectivity for SailPoint Identity Security Cloud, Microsoft Entra ID, Okta, One Identity Manager and OpenText Identity Manager, formerly NetIQ.

How long does an ASSA ABLOY CLIQ integration with an IAM system take?

A standard integration is live in under two hours. Key2XS connects to the IAM system and the CLIQ environment through pre-built connectors, so no custom development is required.

ASSA ABLOY CLIQ Integration | eCLIQ and PROTEC2 CLIQ

One CLIQ ecosystem, both product lines

CLIQ is ASSA ABLOY's electronic key technology: intelligent keys with embedded electronics, cylinders that need no wiring, and central administration of access rights and audit trails. Two product lines run on it:

eCLIQ is the fully electronic line. Every key and cylinder is electronic, with access rights programmable per key and a complete audit trail.
PROTEC2 CLIQ combines the mechanical ABLOY PROTEC2 disc cylinder platform with CLIQ electronics. One key operates both the electromechanical CLIQ cylinders and the mechanical PROTEC2 cylinders in the same estate, which makes it a popular choice for organizations extending an existing PROTEC2 installation.

Both lines are administered through the same CLIQ management environment, and Key2XS supports both. If your estate mixes eCLIQ areas with PROTEC2 CLIQ areas, one integration governs it all.

CLIQ controls the keys. Who controls the rights?

CLIQ solves the hardware problem brilliantly: no wiring, time-limited validity, lost keys that can simply be blocked, and an audit trail per key. What it cannot know is who should have which rights in the first place. That knowledge lives in your IAM system, in roles, contracts and approval decisions.

Without a connection between the two, administrators re-enter identity decisions by hand in the CLIQ administration:

A leaver is deprovisioned in the IAM, and someone must remember to block the key too
A role change grants new application access automatically, but the matching key rights are a ticket in someone's queue
Auditors ask why a key holds certain rights, and the answer lives in an email from two years ago
Time-limited validity and revalidation are configured per key, but disconnected from the contract dates and lifecycle events your IAM already knows

Key2XS closes that loop. The IAM decides, CLIQ enforces, and Key2XS keeps the two in sync 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

Connect. Key2XS connects to your CLIQ management environment and to your IAM system through their standard interfaces. A standard integration is live in under two hours, with no custom development. Your locking plan, cylinders and keys remain exactly as they are.
Map. Roles and groups in your IAM are mapped to CLIQ access rights. A role like “Field Technician - Region North” can correspond to precisely the substations, street cabinets and padlocked perimeters that role requires, whether those are eCLIQ or PROTEC2 CLIQ cylinders.
Orchestrate. Lifecycle events in the IAM, such as onboarding, role changes, contract expiry and offboarding, are applied to CLIQ key rights in near real-time. Revoking an identity withdraws its physical access in the same movement.
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 certified, pre-built connectivity on the identity side as well:

SailPoint Identity Security Cloud (Key2XS is a certified SailPoint Technology Alliance Partner)
Microsoft Entra ID
Okta
One Identity Manager
OpenText Identity Manager, formerly NetIQ

The same platform also governs iLOQ, so organizations running CLIQ at one site and iLOQ at another manage both from a single identity-driven flow.

Built for critical environments

CLIQ systems are typically found where access matters most: utilities, telecom, transport, government, healthcare and industry. Key2XS is built for exactly those environments.

Certified by ASSA ABLOY. The Key2XS integration with the CLIQ ecosystem is certified by ASSA ABLOY, so it is validated against the locking technology you already trust.
NIS2 and CER ready. A continuous, tamper-evident audit trail links every physical access right to an identity and a policy decision.
Built for continuity. The Key2XS platform is engineered for 99.99% availability, matching the uptime expectations of critical infrastructure operations.
Security by design. All communication is encrypted in transit with TLS 1.3, and data at rest is protected with AES-256.

Identity-driven key management for ASSA ABLOY CLIQ

One CLIQ ecosystem, both product lines

CLIQ controls the keys. Who controls the rights?

How the integration works

Works with the IAM system you already run

Built for critical environments

Frequently asked questions

See your IAM and ASSA ABLOY CLIQ working together