Town halls and civic offices, but also archives, depots, pumping stations and traffic installations. Key2XS connects the IAM you already run to the keys already on those doors, accountable to the standards you answer to.
Civil servants, consultants, outsourced services, event crews and field teams all need keys. Every arrival and departure is a change the key administration must catch, and it rarely catches all of them.
Facility and cleaning staff rotate without a leaver process you ever see.
A six-month contract lives on in the key registry for years.
People move between departments; the old access quietly remains.
A spreadsheet one person understands, until they retire.
When something happens in an archive or a pumping station, one question is asked publicly: who could enter here, and on whose authority?
Middleware between your IAM and the locks already on your buildings and installations. Follow one facilities contract through four events.
The contract in your IAM becomes access rights for exactly the contracted buildings. No key handover, no spreadsheet.
The scope changes; the rights change with it, in one movement, near real time.
An event adds doors for one evening on top of the running contract. Granted through the event assignment, ended with it.
The end date in the IAM closes every door on the estate in the same movement, and logs it. No exit checklist item, no key living on in a drawer.
NIS2 brings public administration entities into scope, including appropriate policies for access to premises. Municipalities running critical infrastructure can face CER. Both ask for the same thing: governed, current, demonstrable.
A pumping station or a traffic cabinet sees a key long before it sees a network. Rights travel with the key, and a withdrawal is enforced at the next key update.
The next time the key is used or updated it picks up its new rights. Revocation propagates the same way.
Near real time, not instantaneous. Each key system closes the window with its own mechanism; Key2XS makes the decision centrally and logs the change.
Middleware through standard interfaces. Locks, keys and the locking plan stay as they are.
Identity decisions become access rights, with evidence.
NIS2 brings public administration entities into scope and requires appropriate policies for access to premises. Key2XS enforces physical access through identity and policy and produces the audit trail that demonstrates it.
Yes. Access follows the assignments and end dates in your IAM system. When a contract ends, the corresponding access rights are withdrawn automatically and the change is logged.
Yes. Key2XS governs access rights centrally regardless of location type. Civic buildings, archives, depots and outdoor installations are all mapped to roles in the same flow.
No. Key2XS is middleware. It orchestrates access rights through the standard interfaces of your existing key systems: iLOQ, ASSA ABLOY CLIQ, ASSA ABLOY Access or Traka. Locks, keys and the locking plan stay as they are.
A standard integration is live in under two hours, through pre-built connectors, with no custom development required from your team.
A guided walkthrough of how identity, policy and physical keys come together across a public estate.
