Buttons and QR codes

The nine single-purpose tiles in one place — booking actions, visitor self service and registration, guest Wi-Fi, wayfinding, room control, the door and the screen's language — with each one's settings.

Updated 19 Aug 2026

One tile, one job. These are the small widgets that fill the action-button tiles — each puts a single thing to press, or a single code to scan, on the screen. This page covers all nine; the places themselves and the settings that apply to the whole design are in Widgets and the places they go.

Booking buttons

Check in, check out and extend, as tiles. The buttons act on the bookings of the resources you point them at, and each action appears only if you turn it on.

Can go on: Action buttons

Setting	What it does	When to change it
Resources	Which resources’ bookings the buttons act on — Follow device location, All resources, By building, By floor or Specific resources. Following the device, an Auto scope row narrows it to Smart, This room, This floor or This building	Leave it following the device on a screen beside the room it serves; pick specific resources for a kiosk that fronts several
Type	Narrows the chosen resources to one resource type; empty means Any resource type	The location mixes rooms and desks and the buttons should serve only one kind
Show check-in	The tile that confirms a booking on arrival. Open door on check-in additionally releases the Door you pick at the same moment	Hide it where check-in happens at the room’s own panel or in the app
Show check-out	The tile that ends a booking and frees the resource. Open door on check-out works the same way as its check-in twin	Hide it where bookings simply run out on their own
Show extend	The tile that lengthens the booking that is running	Hide it where back-to-back bookings leave nothing to extend into

Visitor self service buttons

Reception without the receptionist: walk-in registration, check-in, check-out and re-check-in as tiles, with an optional guest Wi-Fi service. On an action tile it stays compact; on the main stage the services spread out beside a walk-in QR code, so a guest can also do everything from their own phone.

Can go on: Main stage · Action buttons

Setting	What it does	When to change it
Show walk-in registration	A guest without an invitation registers at the screen. Need to check-in after register keeps a separate check-in step afterwards, on this panel or at reception	Turn the second one on where reception still wants to see everyone who registered
Show check-in	The tile an invited guest checks in on	Hide it where guests check in by scanning a code instead
Show check-out	The tile a leaving guest checks out on	Hide it where nobody is expected to sign out
Show re-check-in	Lets a guest who already checked out come back in without registering again	A site guests leave and re-enter during the day
Print visitor badge label	A badge label is printed for the guest	A label printer is connected at this screen
Location	Which building’s visits the buttons serve — Follow device location, All buildings or Choose…	Leave it following the device unless one screen serves several buildings
Show guest Wi-Fi	Adds the guest network as a service. Wi-Fi source is Enter manually — with Network name (SSID), Password and Security — or Guest Wi-Fi portal, picking the WiFi login page	The lobby doubles as the place guests get online

Visitor registration QR code

The touchless walk-in: the guest scans and registers on their own phone instead of touching the screen. It is also what Visitor self service buttons silently becomes on a screen without touch. The full lobby build around this widget — and why Location matters there — is Set up a lobby screen for visitors.

The walk-in registration code on an action tile.

Can go on: Action buttons

Setting	What it does	When to change it
QR action	Whether scanning registers the visitor only (Register only) or registers and checks them in (Register and check in)	Register and check in where nobody staffs the desk
Check in directly	Skips the confirmation the visitor would otherwise tap through. Refused unless the code carries a valid access key, so it is not independent of the next setting	The shortest possible path matters more than a confirmation step
Access key type	How often the code behind the QR is replaced — Daily, Hourly or Every 3 minutes	A code on a public wall should rotate fast; a code behind a reception desk need not
Print visitor badge label	A badge label is printed for the guest	A label printer is connected at this screen
Location	Which building the registration belongs to — Follow device location, All buildings or Choose…	Leave it on Follow device location

QR Code

A code of your own — a feedback form, a menu, a survey link. The tile renders whatever you give it as a scannable code.

Can go on: Action buttons

Setting	What it does	When to change it
QR code content	The text or link the code encodes	The code should point somewhere new

Wi-Fi QR Code

The guest network as a scannable code — a phone that scans it joins the network without typing anything.

Can go on: Action buttons

Setting	What it does	When to change it
Network name (SSID)	The network the code joins	The guest network changes
Password	The password the code carries	Rotating the guest password — the code updates itself
Security	The network’s protection, WPA or WEP	Only if the network is not WPA
Description	The caption under the code while the credentials are hidden; empty, the tile just says to scan	Saying which network it is, or who it is for
Hidden network	Marks the network as hidden, so a phone can still find it after scanning	The SSID is not broadcast
Show SSID and password	Replaces the caption with the name and password, for typing them in by hand	Guests whose phones cannot join from a code

Wayfinding QR code

Scan it and directions open on the reader’s own phone, starting from where this screen stands — for anyone in the building, not just visitors. It has no settings of its own beyond the shared ones.

Can go on: Action buttons

Room control QR code

During a booking, the code lets the people in the room control its equipment from their own phone. The code is itself the touchless path, so this tile stays on screens without touch. It has no settings of its own beyond the shared ones.

Can go on: Action buttons

Open door button

One door, one press. The tile is captioned with the door’s own name — a design can carry several of these — and the press asks the person to identify themselves before the door opens. With no door picked, or nobody allowed, the tile goes quiet.

Can go on: Action buttons

Setting	What it does	When to change it
Door	The door the button releases; its name becomes the tile’s caption	Every tile needs one — add more tiles for more doors
Allow users	Lets staff identify themselves and open	Off where the button is for guests only
Allow visitors	Lets a visitor open with their visitor badge	Off where the door is staff-only
Who can open	Everyone allowed above, or only Today’s booking participants — with Participant resources naming the resources whose bookings count	The door guards meeting rooms rather than the office entrance

Language selection

The screen’s display language, changed at the screen — each language listed in its own script.

Can go on: Action buttons

Setting	What it does	When to change it
Design	List shows the languages right on the tile, one tap to apply; Button is a single tile that opens a chooser	List for two or three languages; Button where the list would outgrow the tile
Limit languages	Restricts the choice to the Language entries you pick, instead of everything the system offers	The site really uses two languages, not the whole list

What this does not control

What there is to act on. A check-in button needs a booking, the visitor tiles need the Visiting module’s records, and the door button needs a door set up in access control. None of that is created here.
Their size and colour. The design-wide font size, appearance and widget background apply to these tiles like everything else — see Widgets and the places they go.
Where the screen thinks it is. Everything set to Follow device location reads the device’s location, not the content’s.