The visitor app

A web app for the people who are in your building but do not work there: visitors, contractors, anyone handed a link at reception. The same app has a staff side behind a sign-in, covered at the end.

It is served from your own instance at /v/ — a static app, so there is no install, no account and no app store. A link or a QR code is enough, and the version a visitor gets is the version your instance is running.

What a visitor can do with it

See the floor. The app draws the venue's floor plan from the same walls, doors and zones you drew in the Designer — not a photo of it — and lets the visitor switch floors. Only the zones you allow are drawn.

Get directions. The visitor picks where they are and where they want to go, and the app draws a walking route between the two, through the doors on the plan and — between floors — through the lifts and stairs you have set up as floor connections. A step-free option leaves the stairs out.

The app does not know where the phone is

A web page cannot listen for beacons, so the visitor tells the app where they are by picking a room. The route is drawn from that. There is no live dot following the visitor, and nothing about the visitor's position reaches the platform.

Register a visit. Where the building runs Visitor Management, a Register your visit card asks who they are, which host companies they are visiting, the companies' own questions and the terms. The card then shows the visit's status, and the QR to show at reception appears the moment a host company approves. Only this phone can see its own visit.

Report something. "Something not right?" — a spill, a broken light, a door that will not open — goes straight into the Facility app's request inbox, with the room the visitor tapped as the location. Reports are anonymous unless the visitor leaves a name or number. Visitors cannot mark a report urgent; that stays a staff decision.

Get notices. The app checks every half-minute and shows, as a notification on the phone, updates to the visitor's own reports as the team works on them, and meeting-room activity on the floor the visitor is on (and only in zones on the visitor whitelist, if one is set). Other people's reports and rooms on other floors are not shown.

Register a visit and check in. With Visitor Management enabled, the visitor registers who they are and who they are visiting, watches the approval arrive, types the code on the badge reception hands them to check in, gets directions to their host's floor, and checks out when they leave.

End the visit, which forgets the venue on that phone.

How a visitor gets in

Registration is by venue QR code: each venue has a token, printed as a QR on the Mobile App Management page. Scanning it opens the app with that token; the phone posts it, gets a visitor-tier access token back that lasts thirty days, and is bound to that venue. A visitor can also type the venue code by hand.

That is why a QR code by the door is all it takes. It is also why the token matters: it is the thing that decides which building somebody has joined, so treat it as you would the TV dashboard's share link. Rotate it to issue a new code, or revoke it to stop new scans — either one also ends every open visitor session for that venue, so a code that has gone somewhere it should not can be shut off in one click.

A visitor token is scoped, deliberately

A visitor's access is its own tier. It can see the venue it registered against and the other floors of the same organisation, the zones on the whitelist, and the two things above — reporting and notices. It is not a staff account with a friendlier screen.

What you configure

Apps → Your apps → Mobile App Management, one page per organisation:

Setting	What it changes
Welcome message	Shown when a visitor first opens the venue
Brand colour	The app's accent, so it looks like your building
Visible zones	Which zones the app will draw at all. Empty means every active zone
Venue QR codes	One printable code per venue, with its URL to copy, and the rotate / revoke buttons
Floor connections	The lifts, stairs and walkways the router may use between floors — each one placed on every floor it serves

The default for visible zones is everything, so this is a setting to make a decision about rather than one to leave. A visitor should be able to find the meeting room they came for; they have no business seeing the layout of the executive floor or the location of the security office.

Before it is useful

• A venue with a drawn floor plan — walls, doors and zones — or the map is empty and the router has nothing to walk through. Floor plans and positioning.
• Doors between rooms. The route follows the plan; a room with no door drawn is a room the router cannot enter.
• Floor connections, if visitors need to move between floors.
• A decision about the whitelist.
• The Facility app, if you want visitors to be able to report problems.

The staff side

The same app, opened without a venue code, offers sign in for app users: organisation, email and password. It is a phone-sized view of the things a person on their feet needs:

• Home — devices online, requests today, recent alerts.
• Alerts and Requests — the alert feed and the work-order queue.
• Your apps — the mini-apps assigned to that user's role: Meeting Room (which rooms are free, and a quick booking from the phone) and Facility (the work orders). A restroom-queue mini-app exists in the code as a demo with nothing behind it; the app does not show it.

If Your apps is empty, the user has no mini-app grants — the same permissions that gate the web apps.

Where it meets the rest of the platform

• Facility — a visitor's report is a tenant request like any other, and the status the team sets is what the visitor sees.
• Meeting Room — bookings feed the visitor's notices, and staff can book from the phone.
• Visitor Management — the module that will own the front desk side of this: who is here, who approved it, host notification.

When it disappoints

The map is blank. The venue's plan has no zones drawn, or the zones the visitor needs are not on the whitelist.

No route is found. The plan has no door between those rooms — the message says so. Draw the door.

It will not route to another floor. No floor connection joins the two floors, or the only one is a staircase and step-free is on.

"Reporting an issue is not available." The Facility app is not enabled for the organisation.

The venue code is refused. It has been rotated or revoked — print the new one.

The branding did not change. The app caches; reload it on the device.