Skip to content

Access & Attendance

Multi-site access history

Combine entry events from several entrances, buildings or access-control vendors into one consistent, searchable history of who was on site.

Conceptual architecture · illustrative, no real data

What we build

When each entrance or building has its own system, nobody holds the full picture. Answering "who was on site last Tuesday?" means checking several places.

  • One database that merges events from every access system
  • A shared format for people, zones and directions across vendors
  • Matching of card numbers and face IDs to employees
  • Search and export across the full event history

How it works

A typical data flow, from your equipment to the place the data is used.

Conceptual architecture · illustrative, no real data

  1. Site A · Site B · Site CYour systems
  2. Stackline consolidationStackline software
  3. Single event historyWhere the data goes
  4. Reports and searchWhere the data goes

Getting started

What we need from you

  • A list of the access systems and sites involved
  • Access to each system's events (API, database or exports)
  • The employee list or directory used for matching

What you receive

  • A single history of entry and exit events across sites
  • Written matching rules for people and zones
  • A handover session with your IT team

Questions

Each feed is converted into the same structure: person, zone, direction and time. Reports never see the difference.

In a database on your server or in an environment you choose. The data stays yours.

Against your employee list or directory. The matching rules are written down, so your team can see exactly how each person is identified.

Yes. Filter the full history by person, door, site or period, and export the result.

Have a similar task?

Send a short note about the equipment and software you use and what should change. We'll answer with questions or a first step.