Access lives in the systems, and not in a policy
Every site runs its own access control system, with its own groups, its own administrators and its own logic. Nobody owns the rule across all of them.
The platform
One layer above every access system
Nothing is replaced. The decision, the approval and the record move one layer up.
How it fits
Your access systems keep doing what they do best
Identity comes in from the systems that already own it. Decisions go down into the access systems you already run. Evidence comes back up, written as it happens.
Modules
6 things the platform does
Each one stands alone. Together they close the loop between the reason someone is on site and the door that opens for them.
Identity Lifecycle
1 record per person, above every system
Find out more
Contractor Management
No certificate, no badge-in
Find out more
Credential Management
One identity, verified at every reader
Find out more
Self-Service Terminal
One terminal, doing the work of a reception desk
Find out more
Key Management
One credential, and who holds the keys to it
Find out more
Audit & Evidence
Evidence, not intentions
Find out more
The landscape today
Access is still managed by system, site by site, by hand
4 patterns we find in almost every organisation before we start.
HR knows first, security finds out later
Joiners, movers and leavers are re-keyed by hand. Rights outlive the reason they were given, and it usually surfaces during an audit.
Contractors are managed on paper
Certificates, inductions, permits and insurance sit in inboxes and spreadsheets, verified at the gate, by a person, under time pressure.
Audits are reconstructed afterwards
Proving who approved which access, and why, means exporting from several systems and piecing the story together.
Why now
4 pressures arriving at the same time
None of them are going away, and none of them are solved by another access control system.
Regulation with teeth
NIS2, ISPS, food defence, DORA, GDPR. Access rights are no longer an operational detail. They are evidence you have to produce.
Most people on site are not staff
Contractors, temps, service partners, drivers and visitors. The population you control least is the population you must control best.
The credential left the card
Mobile and biometrics arrive while the existing card base still has to keep working. Both have to live in one lifecycle.
Security became an IT conversation
Identity governance, single sign-on, data residency, no unmanaged servers. IT now has a veto on physical security projects.
Choosing a platform
6 questions worth putting to any supplier
Every platform in this category answers them differently. These are our answers, and each one can be checked.
| Ask | Axxession |
|---|---|
| Does it govern the access control systems already installed at our sites? | 7 working integrations today, including European systems such as Nedap AEOS, primion GET and Equans I-CARDS. Working integrations, not certified ones. |
| Who do we contract with, and under which law? | No parent or shareholder outside the EU; your contract is with a Belgian entity, governed by Belgian law. |
| Where is the service hosted? | Hosted in European Union data centres. |
| Who holds the keys to our credentials? | You do. The keys stay in a secure module under your control, or escrowed to you. |
| Are staff, contractors and visitors on one record? | Yes. One identity record per person, with the credential and the self-service terminal on the same platform. |
| Is the supplier certified? | ISO 27001 certification in progress. |
Keep reading
Where to go next
Questions
Frequently asked questions
Is Axxession an access control system?
No. It is the governance layer above access control systems. Readers, controllers and panels stay exactly as they are. What changes is where the decision is made, who approves it, when it ends, and where the record lives.
Can we start with only one module?
Yes. Each module stands alone. Most organisations start with the problem that is hurting, contractors, or visitors, or the audit finding with a date on it. The rest follows once that 1 has earned its place.
How does the platform connect to our HR system?
Through one standard connection using SCIM 2.0 or file exchange, set up the way your IT team already connects any other business application. There is no development project and no second copy of your people data.
The first step
Start with 1 site and 1 population.
You judge something that runs on your own site. Your access systems and readers stay where they are. If it earns its place, we extend it site by site.
One siteOne populationYour readers stay