Skip to content

Aahlan — in-house product

Aahlan VMS: bilingual visitor management, from invitation to gate

Aahlan VMS is the visitor management platform we designed, built and run ourselves, in Arabic and English. It covers the whole visit — invitation, walk-in, host approval, QR pass, gate check and check-out — and keeps a record of every decision.

Built by Aahlan

Built and operated by Aahlan. Every capability described here exists in the product today.

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.

What we built

What we built

  • 01

    Invitations and walk-ins

    Hosts send an invitation; the visitor confirms their details on a public page, with no account needed, and receives a QR pass. Reception registers walk-ins in one form, choosing from 10 visitor types — guest, client, VIP, contractor, vendor, delivery and others — with group passes for people arriving together on one QR.

  • 02

    Host approval and blocklist

    A pass can require the host’s approval, and the gate treats it as awaiting approval until the host decides. Administrators keep a blocklist with optional expiry dates; a visitor who matches it is stopped at the scan, and the host and issuer are alerted.

  • 03

    Gate verification

    Guards scan the QR with a camera or type the code, on the web security portal or in Aahlan Guard. The result is explicit — valid, expired, revoked, awaiting approval, blocklisted, wrong gate and others — and check-in, check-out and denial are one tap each. A guard assigned to one gate can verify only at that gate.

  • 04

    Dashboards for reception, hosts and administrators

    Reception sees arrivals, visitors inside and pending approvals. Hosts see their own visitors and decide approvals. Administrators get a site overview, a filterable pass list with CSV export, reports, and a console for gates, employees (with CSV import), notification providers and data retention.

  • 05

    Audit trail

    Every scan and gate decision is written to a gate log. Security events — sign-ins, two-step verification, data exports and administrative changes — go to a hash-chained audit log, and the compliance page shows whether the chain is intact.

  • 06

    Passes and the Outlook add-in

    Visitors receive their pass as a QR code, a PDF badge or an Apple Wallet pass, through a share link that expires. The Outlook add-in lets a host issue a pass from an e-mail, prefilled from the message, and insert the QR into the reply.

By the numbers

Staff roles
8
From organisation admin to security guard and employee host
Visitor types
10
Pass token length
192 bits
Interface languages
2

Where it stands

Aahlan VMS is built end to end. Invitations, walk-ins, host approval, gate verification, check-out, the blocklist, dashboards, reports and exports have all been tested from start to finish, and role permissions are checked on every route. It is ready for pilot deployments with organisations that want to replace a paper or spreadsheet visitor log.

Some parts depend on each deployment. In-app notifications are always recorded; e-mail, SMS and WhatsApp messages go through the providers each organisation connects, and the platform reports a failed send rather than pretending it went. Apple Wallet passes are signed with the deployment’s own Apple certificates.

More case studies

All case studies

Have a process that should run itself?

Tell us about it. We will help you work out whether AI is the right answer, what it would take, and what it should return.

Newsletter

Practical AI, in your inbox.

Real use cases, Saudi regulations and what works in Arabic — once or twice a month. No spam; unsubscribe any time.

We’ll e-mail you to confirm. Unsubscribe any time — see our privacy policy.