SECURITY COMMAND
Command dashboard
Online
--:----
LIVE SECURITY POSTURE
Access intelligence is ready.
Monitor active occupancy, gate throughput, verification health and exception pressure across the current client estate.
LIVE
7-DAY FLOW
ENTRY CONTROLGate activity trend
TODAY
LIVEHourly movement
VERIFICATION FABRIC
Intelligence service health — last 24 hours
Access Intelligence TerminalSECURE FRONTLINE WORKSTATION
Online
IDENTIFICATION
Who is at the gate?
Ask for one authoritative starting identifier. Do not ask the visitor to tell you information the platform can resolve itself.
ID
ALIEN
ADAPTIVE AUTHENTICATIONSTEP-UP VERIFICATION
Confirm the person without teaching the answers.
One response per challenge. Wrong answers are never revealed and are not erased by later questions.
VERIFICATION ATTENTIONA verification response needs attention.
Challenge 1PENDING
Waiting for identity resolution…
Registered contact possession
Select a masked destination already associated with this identity.
VERIFIED PROFILE & MOVEMENTEXPECTED VEHICLE
VISITOR
Authenticated person
—
How is this person entering?
Vehicle record
Verify the visible vehicle characteristics
Inspect only what can reasonably be observed at the checkpoint. Registry year is intentionally not used as a visual check.Complete the visible checks below.
VISIT CONTEXT
Where are they going, and how can security reach them?
Visit contacts are operational information for this visit only. They do not overwrite authoritative identity records.
ACCESS RECOMMENDATION
Calculating…
The risk engine is comparing authentication, local history, resident status, vehicle evidence and site policy.
Risk——
Confidence—Authentication/evidence
EXIT CONTROL
What is leaving the premises?
QUICK PEDESTRIAN EXIT
Record exit without repeating entry-level authentication
This option follows the site policy. Vehicle exits always remain authenticated and custody-controlled.
Identify the person leaving
ID
ALIEN
EXIT AUTHENTICATION
Verify the current person.
VERIFICATION ATTENTIONA verification response needs attention.
ChallengePENDING
Waiting…
Step-up verification
CUSTODY & RELEASE
Evaluating presence…
Original custodian authorization required
Send a release code to the verified authorization contact established at entry.
Ready to record exit
The current authentication and custody evidence will be written to the premises ledger.
LIVE STATE, NOT A SUBSTITUTE FOR HISTORY
Presence answers “what is inside now”; the Access Log answers “what happened over time.”
Administrative corrections are separately audited and never erase the original movement history.
LAST REFRESHWaiting
People and vehicles are tracked independently.A person may leave on foot while their vehicle remains inside.
Administrative reconciliation is explicit.Authorized admins may declare a stale presence exited, with reason and audit evidence.
Custody is not ownership.The system tracks who physically brought a vehicle in and who attempts to remove it.
PEOPLE
LIVECurrently inside
| Person | Class | Site | Destination | Entered | Risk | Actions |
|---|
VEHICLES
CUSTODY-AWARECurrently inside
| Vehicle | Site | Custodian | Entered | Custodian present | State | Actions |
|---|
ACCESS BOOK
AUDITABLEPeople & vehicle movement history
| Time | Movement | Subject | Context | Site / checkpoint | Operator | Outcome |
|---|
AUTHORIZATION LAYER
Membership links a verified identity to this site.
Identity intelligence remains external; the resident register stores only site authorization context.
1IdentifyResolve identity
→2AuthenticateVerify the person
→3MembershipMatch site resident
→4PolicyApply access rules
RESIDENT DIRECTORY
Site memberships
0 MEMBERS
| Resident identity | Membership | Unit / reference | Validity | Status | Actions |
|---|
Who is a host?
A resident, employee, department, reception point or other internal contact a visitor can legitimately be coming to see.
What does it do?
Hosts make destination capture faster and create context for visit history, authorization and incident review.
What it does not do
A host record does not authenticate a visitor or automatically grant access. Identity verification and site policy still apply.
INTERNAL DIRECTORY
CONTEXT ONLYAuthorized visit contacts
| Reference | Name | Unit / department | Phone | Status |
|---|
| Type | Subject | Name | Reason | Severity | Block | Status |
|---|
1OPENReported and acknowledged
→2INVESTIGATINGAssigned, evidence/action underway
→3RESOLVEDImmediate issue addressed
→4CLOSEDReviewed and formally completed
TAMPER EVIDENCE
Audit-chain verification
Audit events are cryptographically chained. Integrity verification checks whether historical evidence has been altered.
AUDIT LEDGER
PAGINATEDAccountable security activity
| Timestamp | Client | Actor | Role | Action | Subject | Outcome | Request |
|---|
TENANT TOPOLOGY
Model the physical estate before configuring the security policy.
Sites represent protected locations. Checkpoints represent the actual gates, receptions, pedestrian entrances or controlled bays inside those sites.
SITES
Security locations
Estates, buildings, campuses, factories or other protected locations.
CHECKPOINTS
Controlled access points
Vehicle gates, pedestrian gates, reception desks, lobbies and service entrances.
SITE SECURITY POLICY
Verification, movement & continuity
These controls define how strict the site should be at entry, exit and during degraded connectivity.
PLATFORM TENANCY
Client organizations and service state
Super administrators create, scope and support every client environment from this control plane.
CLIENT ACCOUNTS
Platform tenants
| Client | Code | Package | Subscription | Mode | Status |
|---|
COMMERCIAL CONTROL
Subscription packages and capacity
Prices and limits remain editable. Package codes stay stable so historical subscriptions remain traceable.
MANUAL SUBSCRIPTION CONTROL
Packages
MY WORKSPACE SECURITY
Screen lock preference
Every operator should have their own account.
Roles define the baseline. Site assignments constrain where the user operates. Account changes are auditable.
ROLE-BASED ACCESS
Client users
Search, review and maintain operator identities without recreating accounts.
| User | Username | Role | Site scope | Status | Last login | Actions |
|---|
TRUSTED ENDPOINTS
Approved gate and administration devices
Device trust adds another control layer around sensitive gate operations and administrative access.
DEVICE REGISTER
DEVICE-AWAREGate devices
| Label | Device ID | Platform | Status | Last seen |
|---|