Question 1

What is a Visitor Management System (VMS)?

Accepted Answer

A Visitor Management System replaces the paper visitor logbook with software that pre-registers visitors, verifies their identity on arrival, prints a badge, assigns a card, notifies the host, tracks the visit in real time, escalates overdue visits to security, and logs every action for the audit trail. A modern VMS like GLARUS VMS also integrates with meeting-room display TVs, calendar systems (Outlook / Google / Apple), email gateways, and corporate access-control or HR systems via APIs.

Question 2

How does a digital visitor management system work?

Accepted Answer

Five steps. (1) The host pre-registers the visit (or the visitor walks in). (2) Reception verifies ID, captures a photo, prints a badge, and assigns a card. (3) The host receives an email + real-time in-app notification; if the visit is for a meeting room, the meeting display TV updates instantly. (4) Active visits are visible on the reception dashboard with overdue / due-now chips; the system escalates overdue visits to the security team. (5) On check-out (or after auto-checkout closes a stale record), the activity log captures the full visit; daily metrics roll up to dashboards; reports export to CSV / PDF for compliance.

Question 3

What's the difference between a digital VMS and a paper visitor logbook?

Accepted Answer

A paper logbook is a GDPR / PDPL / HIPAA liability — every previous visitor's name, company, host, and arrival time is visible to whoever signs in next. It can't pre-register, can't notify, can't escalate, can't audit, can't scale, and can't prove who was on site at any given moment. A digital VMS encrypts visitor data, restricts access per role, automates host notifications, captures photos for incident review, tracks cards in inventory, logs every action with actor and timestamp, and exports audit-ready reports on demand.

Question 4

Why does pre-registration matter?

Accepted Answer

Pre-registration moves the friction out of the lobby. The host submits the visit details from the web app; the visitor receives an ICS calendar invite (which adds to Outlook / Google / Apple Calendar) and a pre-visit email reminder at a configurable lead time. On arrival, reception confirms the visitor in 30 seconds instead of taking 3 minutes of typing — which means lobby throughput at a busy bank or government office goes up 3 to 4×. Pre-registration also unlocks the meeting-room display integration: as soon as the visit is approved, the meeting room TV picks it up.

Question 5

How does the meeting room display integration work?

Accepted Answer

GLARUS VMS ships with a paired Meeting Display companion app that runs on TVs / kiosks in meeting rooms and lobbies. Each screen maps to one or more areas; when a reservation is created, checked in, or checked out, the meeting display refreshes in under a second. The TVs show upcoming meetings, the currently-live meeting (with the visitor and host), and recently completed sessions. The display app is read-only and token-authenticated — it never writes data, so it can't be tampered with from the lobby.

Question 6

Does the VMS integrate with our calendar and email system?

Accepted Answer

Yes. Email is delivered over standard SMTP or Microsoft 365 — both are first-class transports. Calendar invites are standards-compliant ICS files plus a Google Calendar "Add to calendar" link in the invitation, so the visitor can add the meeting to Outlook, Google Calendar, or Apple Calendar with a single tap. Timezone is configurable, with an option to force UTC for organizations that prefer that. All outbound email goes through a resilient outbox with retry, so a temporary mail-server outage never loses a notification.

Question 7

How are visitor cards managed?

Accepted Answer

Each card is a row in the database with a state — `ACTIVE`, `LOST`, or `RETIRED` — plus an assignment history. When reception assigns a card to a visit, the card moves to that visitor; when the visitor checks out (or is auto-closed), the card returns to the active pool. Lost or retired cards are taken out of rotation. Card lookup is rate-limited and role-gated (Reception / Admin / Building Manager only) to prevent enumeration attacks. The full card-assignment history is available in the audit trail.

Question 8

What happens if a visitor doesn't check out?

Accepted Answer

Two safeguards. First, the dashboard shows an "overdue" chip on any visit past its expected duration so reception can prompt the visitor or the host. Second, every 15 minutes a cron job auto-closes visits past the configured threshold (default 4 hours) and writes the event to the audit log. A separate escalation job notifies the security team email when a visit goes past the overdue window, so the on-site security team can investigate while the data is still fresh. The result: your reports never show 47 visitors on-site when really there are 12.

Question 9

Can the VMS handle multiple buildings or campuses?

Accepted Answer

Yes — it's built for it. The data model is Building → Department → Host, plus Building → Area for room-level capacity. Users are scoped to specific buildings or departments via the role system, so a Building Manager only sees their site and a Department Manager only sees their department's hosts and visitors. Reports filter by building, department, host, area, or visit type. Meeting displays map to one or more areas per screen, so a multi-campus deployment can run hundreds of TVs from one central instance.

Question 10

How is role-based access controlled?

Accepted Answer

Five distinct roles: Admin (everything), Building Manager (one or more buildings), Department Manager (one or more departments within their buildings), Reception (front-desk check-in flows), and Basic Access (read-only). Access is enforced at the route level, so even a forged URL won't leak data. Sessions use signed tokens with a fixed lifetime and inactivity auto-logout. Every sensitive action (mail test, card lookup, login attempts) is rate-limited.

Question 11

Is GLARUS VMS GDPR, HIPAA, PDPL, and ISO 27001 compliant?

Accepted Answer

The platform is designed to meet GDPR (EU / UK), HIPAA (US healthcare), PDPL (Saudi Arabia, UAE), and ISO 27001 controls. Personal data is encrypted in transit (TLS) and at rest. The full activity log records who did what to which record at what time. Configurable data-retention windows + a right-to-be-forgotten workflow let you honor subject-access requests in minutes. Role-based access, rate limiting, and 2FA on admin accounts close the technical surface. For regulated environments, on-premise deployment keeps every byte of personal data inside the customer's own data centre.

Question 12

Cloud or on-premise — which do most customers pick?

Accepted Answer

Both are available. Most commercial customers (banks, retail HQs, technology companies) pick the managed cloud edition for speed of deployment and zero ops overhead. Regulated environments — government ministries, defence sites, hospitals running EHRs on-site, embassies, and critical-infrastructure operators — go on-premise so all personal data stays inside the customer's perimeter. The application code, the operator experience, and the meeting-display integration are identical in both models.

Question 13

How long does VMS implementation take?

Accepted Answer

A single-site pilot with the standard channels (reception terminal, host pre-registration, email notifications, card inventory, audit trail) typically goes live in 3 to 4 weeks: 1 week discovery and data model (buildings, departments, hosts, areas, capacity rules, role policy); 1 week configuration and branding; 1 week integration (email gateway, identity, optional access-control); 1 week UAT plus training. Multi-site rollouts add ~1 week per wave of sites using the same templates. Meeting-display integration is an additional ~3 to 5 days. Custom integrations and on-premise deployments extend the timeline; our team sizes each engagement up front.

Question 14

How do escalations work for overdue visits?

Accepted Answer

Every 30 minutes a scheduled job scans active visits older than the configured overdue threshold (default 4 hours). If any are found, a single consolidated email goes to the security distribution list with visitor name, host, area, expected end time, and a deep link back into the reception cockpit. The escalation job is rate-limited and idempotent — a network blip won't double-page security. Once a security team-member acknowledges or checks out the visit, the escalation drops.

Question 15

Does it support multiple languages?

Accepted Answer

Yes — the UI is fully internationalisable, with native multi-language support including right-to-left layout for Arabic / Hebrew / Urdu. Notification templates are per-locale; the visitor's preferred language can be captured at pre-registration so the ICS invite and reminder are sent in the right language. A single deployment can serve sites in multiple countries from one control plane.

Question 16

How does it scale for high-traffic lobbies (banks, hospitals, government halls)?

Accepted Answer

GLARUS VMS is built on a stateless, horizontally scalable architecture. We routinely run high-throughput deployments where a single site processes thousands of visitors per day. Reception flows are 3 steps to keep wait times short; pre-registration moves the bulk of work off the front desk; rate limits keep the system stable under abuse; the meeting display companion runs entirely off a cached feed so the central platform never gets hammered by TV refreshes.

Question 17

What custom integrations are possible via the API?

Accepted Answer

GLARUS VMS ships with a full OpenAPI specification covering visitors, reservations, hosts, cards, and admin operations, plus authenticated real-time event streams for live consumers. Typical integrations: CRM (Salesforce, Dynamics, HubSpot) for visitor enrichment, HR systems for host directory sync, physical access-control systems (HID, Lenel, Genetec) to provision badges, identity providers (SAML / OIDC) for single sign-on, and BI tools (Power BI, Tableau, Looker) consuming the daily metrics. Custom integrations are built by the Zeour partner network.

Question 18

Is it suitable for embassies, government, and defence?

Accepted Answer

Yes. The on-premise edition keeps every byte of personal data inside the customer's perimeter; the audit trail is configured for evidentiary use; role-based scoping limits each user to their own building / department; the system enforces HTTPS, signed sessions, inactivity auto-logout, and rate limiting on every sensitive action. For diplomatic missions and visa centres we add appointment-driven pre-registration, passport-number visitor identity, multi-language ICS invites, and a hardened reception flow with photo capture and badge printing.

Visitor Management System

Comprehensive Visitor Management

Understanding Visitor Management — Built on the GLARUS VMS Platform

Key Functionalities

Pre-Registration & Walk-In Flows

Identity Verification & Photo Capture

Building → Department → Host Hierarchy

Area Capacity & Reservation Overlap

Smart Card Inventory (Active / Lost / Retired)

Host Notifications

Calendar Invites (ICS)

Pre-Visit Reminders & Security Escalations

Auto Check-Out for Forgotten Visits

Meeting Room Display Integration

Activity Log & Compliance Reporting

Role-Based Access + Multi-Site Scoping

Software Components

Operator Applications

Reception & Admin Backend

Meeting Display Companion

API & Integration Layer

OpenAPI Specification

Real-Time Event Stream

Live Display Feed

Authentication & Security

Signed Sessions + Role-Based Access

Rate Limiting & Idempotency

Display Access Tokens

Email & Calendar

Email Outbox with Retry

SMTP or Microsoft 365 Transport

ICS Calendar Invites + Google Calendar Link

Operations & Observability

Scheduled Tasks

Activity Log + Daily Metrics

Health Monitoring & Process Management

Hardware Components

Reception & Self-Service Points

Reception Touchscreen Terminals

Visitor Self-Service Kiosks (KIOSAPP066, AUTO666)

Webcam / Camera for Photo Capture

Badge & Card Equipment

Thermal Badge Printer (60 / 80 mm)

RFID / NFC / Barcode Visitor Cards

Meeting Room Displays

GRAVIA Display Controller (GRAVIA06)

Meeting Room TVs (HD or 4K)

Per-Counter Lobby Screens (CounterDSA)

Branch Infrastructure

CONT06 Industrial Branch Server

Glarus_Hub (PoE / RS485 Infrastructure)

Visitor Management Architecture — GLARUS VMS Platform

Tier 1 — Customer & Visitor Channels

Tier 2 — Central Plane

Tier 3 — Site Stack (per location)

Real-Time Update Pipeline

Visitor Management vs Paper Logbook vs Sign-In App vs Access Control — What You Need

Visitor Management System (VMS)

Paper Visitor Logbook

Consumer Sign-In App

Physical Access Control System

Visitor Management System — Deployment Checklist

1) Discovery & Data Model

2) Central Configuration

3) Site Wiring

4) Host & Reception Launch

5) Optimize, Measure & Scale

Visitor Management System Gallery

Why Paper Visitor Logbooks Fail

Paper Logbooks Are GDPR / PDPL Liabilities

Encrypted Database + Per-Field Access Control

Reception Bottlenecks at Peak Times

Pre-Registration Eliminates the Front-Desk Queue

No Real Audit Trail

Every Action Logged with Actor + Timestamp + Metadata

Lost Cards Cost Money + Risk

Smart Card Inventory with State Tracking

Forgotten Check-Outs Skew Reporting

Auto Check-Out + Overdue-Visit Escalation

Disconnected Visitor + Booking + Display + Access Control