Site security
Join gate entries, badge scans and site events to help teams review access gaps.
Example tags
What you can learn
- Badge denied, then door opened within 1 minute
- Visitor checked in, no exit recorded by closing
- Door held open after a permitted entry
- After-hours entry on 3 nights this week
- Camera movement with no matching badge scan
- Visitor booking followed by a gate check-in
Built from recorded events, using the rules we agree with you.
Say what you want to learn. See how it is defined.
DataGlue shows the formula: which events count, in what order, and over what time. Our team builds and checks it with you.
This is an example rule. Your event names, time limits and links are agreed in the build.
Example formulaEvents → tag
Flag a door opening after a denied entry.
- Access control: badge denied
- Door sensor: door opened
- Camera: doorway movement recorded
In this order, within 1 minute, at the same door; staff review the records.
Tag created
Denied entry, door opened
Start with a question that matters.
Review a door opened after a denial
Join a denied badge scan, door opening and camera event for the site team.
Check visitors still on site
Join visitor check-ins and exit records to find visits with no recorded departure.
Spot repeated after-hours entries
Join badge events and site hours to surface repeated entries for review.
Each system adds a piece of the story.
Access control
Badge scans, entry permissions and exits.
Camera events
Recorded gate and doorway movement.
Door sensors
Open, closed and forced-door events.
Visitor records
Bookings, check-ins and host details.
We agree how each source connects through your warehouse, API or the connections in your build. Person records need a shared id to join. Vehicle, shipment, machine and site tags stay on those records.
Send the tag where your team works.
Choose the destination. We build the route so the result can reach the tools your team already uses.
- Security alerts
- Incident tools
- BI dashboards
These are example destinations. The formula stays the same wherever the tag is sent.
Describe the outcome. We’ll join the data.
Bring one site access question. We’ll define the review rule with your team.
A dedicated team builds the connections, rules and destinations with you.