Site Passes

Site Passes: what it does and how it works

Access control for a construction site. It isn’t a list of workers, but a link between the site, people, organizations, zones, passes, credentials, devices and events. Zones: a part of the site, an access level, an owner, rules (days and hours, whether a briefing or clearance is required and for how long). Passes: permanent, temporary, guest, contractor, restricted; the holder is a company employee or a person from Contacts with the site’s organization; blocking, revocation (a reason is required), reissue linked to the previous pass.

Credentials: RFID, NFC, QR or your own code; no two active passes can share a UID, a QR holds a random code rather than personal data, and is drawn in the window without external services. One function on the server decides on access and gives the reason for a denial: unknown card, expired, blocked or revoked pass, outside permitted hours, zone not allowed, no briefing or clearance. The access log is append-only (editing and deletion are blocked by database and endpoint triggers); manual security entries are marked “manual” and signed by the author. Security post from a phone: scan a QR with the camera (if the browser supports it) or type a number, see the decision in large type, log an entry or exit; a denial alerts security once per pass and zone within 10 minutes.

Contractors: assign the organization’s people, zones, dates and an owner, issue and revoke passes in bulk; a contractor sees only the passes of their own people. Passes expiring within the next 7 days are a site issue and a daily notification to whoever issued them. When an organization’s participation ends, the app only warns about its active passes and blocks no one. An honest word on limits: no physical controller, reader or turnstile has been connected or tested — the software logic has been tested.

A device stays “not connected” until it sends a heartbeat itself; only that heartbeat marks the system “online”. The app can’t open a door and doesn’t pretend to: the decision goes back to the device as a response, and the hardware carries it out. Connection is a webhook signed with HMAC-SHA256 (server/adapters).