Personnel and civilian staff
Transferring between units and sites regularly
Every base
One identity, every base
It starts the moment the clearance officer records it, and not when someone remembers at the annual review. Personnel, contractors and visitors, governed from one platform across every site.
Government & Defence
Clearance-driven access control for government and defence
Access should expire when the clearance does
Who is on your sites
Cleared contractors
Working on site for months, employed elsewhere
Suppliers and service providers
Cleaning, catering, maintenance, logistics
Visiting delegations
Short notice, high sensitivity, foreign nationals
What you are held to
National security policy · NIS2
- Access matched to clearance level, and withdrawn the moment the clearance lapses
- Every site and building governed by 1 policy, and never by local practice
- Full traceability of who was where, retained and produceable
Where it breaks today
- Clearance expiry lives in one system and physical access in another, and they never speak
- A transfer between units means access is added at the new site and forgotten at the old one
- Each base runs its own access system with its own local rules and its own local exceptions
Someone whose clearance lapsed last month can still open the same doors this month. That is not a process gap, it is the gap the whole security policy exists to close.
Government & Defence
Scenario
A redeployment between bases
One person, a new unit, a different site, a clearance that renews on a different cycle to the posting.
The posting is the trigger
The move comes from the personnel system, the way every other consequence of a posting already does.
The old access ends
Rights at the previous base are withdrawn on the transfer date, without anyone at that base having to act.
The new access is derived
The new unit, role and clearance level decide what opens. It does not depend on a request to a local administrator.
Clearance drives everything
If the clearance lapses or is downgraded, the access follows it down the same day, at every site.
What changes
- One policy applied identically at every base, whatever access system that base runs
- Nobody holds access at a site they left, because leaving is the event that removes it
- The question 'who could enter this building last March' has an answer, per site and per person
Compliance
The regimes behind this
Questions
Frequently asked questions
Can access follow a security clearance automatically?
Yes. Clearance level is an attribute on the identity record, and access is derived from unit, role and clearance together. If the clearance lapses or is downgraded, access follows it down the same day at every site.
Does every base have to run the same access control system?
No. That is the point of a governing layer. One policy is applied identically across bases whatever access system each of them runs locally, and the local systems keep operating as they do today.
How is a transfer between units handled?
The posting in the personnel system is the trigger. Rights at the previous base are withdrawn on the transfer date. New rights are derived from the new unit and role, with no request to a local administrator.
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