LenelS2 OnGuard and NetBox verified by face
eConnect binds LenelS2 cardholder records to the faces recognized at readers so a credential event becomes a verified identity event rather than an assumption.
How the integration works
Cardholder and badge data from OnGuard or NetBox synchronize into eConnect. Cameras covering readers supply the face, eConnect performs the match, and the result is written back as access context.
Revocations can propagate quickly. When a cardholder is disabled in LenelS2, eConnect can move that identity onto an internal watchlist so badge reuse is easier to surface at the door.
Supporting product visual
eConnect layers on top of the systems a property already runs, binding them to one identity and one investigation record.
What the integration delivers
OnGuard and NetBox sync
Cardholder, badge, and access level records can populate eConnect identity management.
Reader camera verification
The face at the reader can be compared against the credential owner at the time of access.
Revocation support
Disabled cardholders can be surfaced as higher risk identities if they reappear at a door.
Cross site review
Access behavior across multiple facilities can be reviewed per person rather than per badge.
Where teams put it to work
Each page follows the same structure so operators can compare partners quickly: overview, workflow, capabilities, use cases, visuals, and a clear next step.
Credential sharing audit
Access reads that disagree with the recognized face can be reviewed across the estate in one query.
Terminated employee watch
A disabled cardholder reappearing near a secured entrance can be surfaced quickly.
Restricted corridor monitoring
The reader event and the face can be reviewed together when a security question arises.
How the data moves
eConnect reads from the partner platform, resolves identity, and returns intelligence. Nothing on the property has to be replaced to support that workflow.
LenelS2 OnGuard and NetBox
Partner platform
eConnect
Intelligence layer
LenelS2 cardholder data and door events feed eConnect so the access event and the face can be reviewed in one identity timeline.
What changes for the team
The outcome should be a tighter response path, a cleaner investigative record, and better continuity between identity, video, and operations.
One record, one truth
Identity, video, and operational data live in the same investigation record, so compliance requests and legal holds are answered from one place.
Investigations in minutes, not days
A single photo resolves to a timeline, the associated video, and the linked events. Reviewers stop scrubbing footage and start reviewing evidence.
No system to rip and replace
The platform a property already bought, trained on, and budgeted for stays in place. eConnect adds the intelligence layer on top of it.
Bans that actually hold
A person removed once is recognized on the next visit, whether that is next week or three years later. Enforcement stops depending on who happens to be on shift.
Request a demo for eConnect and LenelS2
We can walk through the partner workflow on systems like yours and show how the alert, identity, and video record stay connected.