Verkada Access
What we collect
Badge, phone and PIN entries granted or denied, by door and site, and doors held open, forced open or tailgated.
How it connects
Verkada sends each door activity to a web address you create in ActivityLog.
Your office days, recorded
See your badge-ins and office days without filling in a form.
My office days
Janet Leverling's first and last badge each day this week, with the door, from Verkada. Each office day is counted from her badge-ins, so there is nothing to fill in.
A sign-in that did not match
Janet badged in at 08:40 on Friday, and at 10:15 Entra ID flagged a sign-in from an unfamiliar location. It was an old phone session; she signed it out and the detection was dismissed.
Spot what does not add up
Server-room visits without a ticket, held-open doors, visitors and sign-ins that do not match where people were.
Office days per person
Each person's office days this week, from their badge-ins. People who work remotely show none, which is expected. Visitors and their hosts, from Envoy, are listed alongside.
Things that do not add up
Server-room entries with no change or ticket that day, doors held or forced open, and denied badges. On Tuesday Robert spent 20 minutes in the server room with no change or ticket to explain it. Tickets and changes come from the knowledge base and Azure DevOps.
Badge-ins against sign-ins
Days where a person was badged into the office while Entra ID recorded a sign-in from somewhere else. Most have an innocent cause, such as a VPN or an old session; each one is worth a quick check.
Where the data comes from
Physical access comes from your door system and visitor sign-in. Digital presence comes from Microsoft 365 sign-ins and meetings. Side by side, they show office days and the things that do not add up.
Envoy
What we collect
Visitor sign-ins and sign-outs, who they were visiting, their company and the purpose of the visit.
How it connects
Envoy sends sign-ins and sign-outs to a web address you create in ActivityLog.
Entra ID
What we collect
Sign-ins with location, and risky sign-in detections such as an unfamiliar location.
How it connects
The read-only Microsoft 365 connection, approved once by your Microsoft 365 admin. It reads Microsoft's own audit trail.
Microsoft Teams
What we collect
Meetings attended and calls, with times.
How it connects
The same Microsoft 365 connection.
How it works
-
Collect door, visitor and sign-in activity
Verkada reports every badge-in and door alarm, Envoy every visitor, and Microsoft 365 every sign-in and meeting.
-
Match badges to people
Badge holders and visitor hosts are matched to people by email, the same people who appear in Microsoft 365 and your other tools.
-
Compare
Office days per person, server-room visits against that day's tickets and changes, held-open and forced doors, visitors, and sign-ins from somewhere else while a person was badged in.
-
Act
People get a quiet check when something does not match and can sign out an old session. The office manager follows up the exceptions.
Questions
Is this for tracking attendance?
It records office days from badge-ins, so nobody has to report them. We built it to spot mismatches that matter for security, such as a sign-in from another country an hour after someone badged in at the office. Decide how attendance data is used in your company, and tell your staff.
Do you collect camera footage?
No. We take door and visitor records only: which door, who, when, granted or denied. No video or images.
What about other door systems?
Verkada and Envoy are what this page is built around. Kisi, Brivo and Avigilon Alta can also send door activity to a web address, so they can be added.
Built from
- Verkada Access
- Envoy
- Entra ID
- Microsoft Teams