The challenge
Many offices and event venues still run visitors from a paper book, a spreadsheet or a WhatsApp group. Nobody checks the visitor against an invitation, the host finds out at the last minute, and when security needs to know who was on site last Tuesday, the record is incomplete or lost.
Most visitor tools are built for English-speaking markets. Saudi reception and security teams work in Arabic, handle contractors, deliveries and VIP guests differently, and need the system to work for the guard at the gate, not only for an administrator at a desk.
Our approach
We mapped a visit from the point of view of each person in it — the host who invites, the receptionist who registers walk-ins, the guard at the gate, the administrator who answers for the record — and gave each of them a screen of their own. Every role has its own home page, and staff act only within the sites they are assigned to.
Treat the pass as a security credential
Each pass is a random 192-bit token. The database stores only its SHA-256 hash, so a copy of the database cannot be used to forge an entry. Visitor details are masked wherever the API returns them, and printed badges carry masked fields only.
Arabic first, English alongside
Arabic is the default language and the interface runs right to left; English is one switch away. Every string a user sees lives in a message catalogue in both languages, including the guard app.