The Kiosk Display turns any screen into a self-updating Wi-Fi access point. Unlike a portal — where each guest walks up and taps to generate their own unique credential — the Kiosk requires no interaction at all. It cycles through a pre-generated pool of credentials on a configurable timer, displaying each one as a full-screen QR code. Guests point their phone camera at the screen and connect. No tap, no button, no staff.
Each credential is displayed for the admin-configured rotation interval, then the screen transitions to the next credential in the pool. This limits the window during which any single credential is visible — reducing the chance of it being shared or reused by a second device after the intended guest has connected.
The Kiosk is ideal for lobby TVs, conference room displays, digital signage players, and any location where an always-on, zero-interaction experience is the priority. The passphrase is shown alongside the QR code so laptop users can type it directly — admins can add a custom label to prompt this where needed.
Behind the scenes, QuuPass maintains a credential pool — a set of pre-generated IPSK passphrases. The kiosk cycles through them on a configurable timer, showing each one as a scannable QR code. When a credential expires it is automatically retired and a fresh one takes its place in the rotation.
Mode A stores credentials directly on the Meraki access point and validates them locally — no external server is involved. This means QuuPass receives no signal when a pool credential is picked up by a guest. Without that event, the replenishment logic is blind: it cannot tell an unused credential from one that has already been scanned by dozens of devices.
The result would be a pool that drains to zero in minutes under any real load, with no intelligent way to refill it — the kiosk stalls, and Meraki API calls spike as QuuPass attempts to compensate. Mode A also stores identities directly on the AP hardware, which has a finite capacity ceiling that a credential-cycling kiosk would breach quickly.
Mode B routes every authentication through a RADIUS server. QuuPass receives a RADIUS accounting message the moment a guest connects, which is the precise event used to mark a credential as consumed, decrement the available pool count, and trigger a top-up. This closed feedback loop is what makes reliable, unattended kiosk operation possible — and is why the Kiosk is a Pro-tier, Mode B feature.
If your SSID is currently on Mode A, see the RADIUS Configuration guide to switch it to Mode B before enabling the kiosk.
QuuPass generates a pool of IPSK credentials for the portal before the kiosk goes live. The pool target size is configurable (Portal Settings → Pool tab). A background worker keeps the pool topped up automatically.
The kiosk page loads the next available credential from the pool and renders it as a WIFI: QR code. This happens entirely server-side — the passphrase is never exposed in the page source.
The guest points their phone camera at the QR code. iOS and Android both decode WIFI: codes natively — no app required. The device joins the network immediately.
After the configured rotation interval (default 30 seconds), the display crossfades to the next QR code. This limits how many devices can share any single credential over time.
When a credential reaches its expiry time it is automatically removed from Meraki. Devices that connected with that credential lose access. The kiosk continues with fresh pool credentials uninterrupted.
The kiosk can be enabled in two places:
Click the monitor icon on any Mode B portal card or row in the Portals dashboard. A slide-over drawer opens with all kiosk settings accessible without leaving the page. Changes save immediately.
Open Portal Settings → Kiosk tab for the complete configuration interface, including pool sizing, URL helpers, and embed code generation.
Toggle Enable kiosk display to activate the feature. Once enabled, the kiosk URL and embed code are generated and displayed immediately.
Controls the background of the kiosk page. Four presets are available:
You can also enter any custom hex colour using the colour picker. The transparent option allows the signage player's own background to show through the iframe — useful when Yodeck or similar tools composite layers.
Controls the shape and decoration of the white card behind the QR code.
Classic
Subtly rounded corners. Clean and neutral — works with any background.
Rounded
Heavily rounded card (pill-style). Softer, modern appearance.
Framed
Green-and-dark double border around the card. Reinforces QuuPass branding.
Sets the white space between the edge of the QR code and the edge of the white card, in pixels. Range: 0 – 40 px. Default: 5 px.
Use 0 if you want the QR code to fill the card completely with no margin. QR code scanners can generally decode codes right to the edge, but a small padding improves reliability on low-contrast displays.
Rotation interval (seconds)
How long each QR code is displayed before transitioning to the next credential. Range: 5 – 300 s. Default: 30 s. Set this longer in low-traffic venues and shorter where many guests arrive simultaneously.
Crossfade duration (seconds)
The fade transition time between the outgoing and incoming QR code. Range: 1 – 10 s. Default: 3 s. Set to 1 s for snappier transitions or up to 5 s for a smoother signage feel.
Label text
The instruction line displayed below the QR code. Default: “Scan to connect to Wi-Fi”. Set to empty to hide it entirely. Max 120 characters.
Show network name
Toggles whether the SSID name (e.g. GuestWiFi) is displayed between the QR card and the label. Useful when guests need to confirm which network they are joining.
Two URLs are generated for every kiosk-enabled portal:
/kiosk/{tenant-id}/{slug}?bg=transparentA fully self-contained HTML page served directly — no Next.js layout, no extra CSS. Use this URL in Yodeck or any other signage player as a Website widget spanning the full zone. The ?bg= parameter overrides the stored background colour at display time without a portal save (useful for multi-zone layouts where you need different backgrounds per zone).
/kiosk/{tenant-id}/{slug}/embed?bg=transparentThe same kiosk page served with X-Frame-Options: ALLOWALL, making it safe to embed in an <iframe> on any web page. The Portal Settings page generates a ready-to-paste embed snippet including the correct width, height, and allowtransparency attributes.
Tip — background matching: When using a transparent background the browser or signage player's own background colour shows through the iframe. If you want the kiosk to sit on a dark background without using transparency, pass the hex value directly:?bg=%232E3331 (URL-encoded #2E3331).
When generating the embed code, choose a preset that matches your display zone. The QR code auto-scales to fill the zone — it is always rendered at 62% of the shorter dimension of the iframe, so the exact size matters less than the aspect ratio.
| Preset | Dimensions | Best for |
|---|---|---|
| 1:1 Tiny | 300 × 300 | Small kiosk tiles, sidebar widgets |
| 1:1 Small | 400 × 400 | Low-resolution displays, compact zones |
| 1:1 Square | 600 × 600 | Standard lobby tiles and signage zones |
| 1:1 Square HD | 1080 × 1080 | High-resolution square zones |
| 16:9 Full HD | 1920 × 1080 | Landscape TVs and monitors (default) |
| 16:9 Half HD | 960 × 540 | Half-width landscape zones |
| 9:16 Portrait | 1080 × 1920 | Portrait/vertical screens |
| 4:3 Standard | 1024 × 768 | Older displays and projectors |
| 4:3 Small | 800 × 600 | Smaller 4:3 displays |
| 4K Landscape | 3840 × 2160 | 4K ultra-HD displays |
| Custom | any | Manual width and height entry |
The kiosk standalone URL is designed to work directly inside any signage player that supports a "Website" or "Web Page" widget — Yodeck, Screenly, Rise Vision, and similar platforms.
Create a Website widget
In your signage player, add a new widget of type "Website" or "Web Page". Paste the Standalone URL from Portal Settings.
Set the zone to full screen
Make the widget zone fill the entire screen or the area you want the QR to occupy. The QR code scales to 62% of the shorter dimension of the zone automatically.
Match the background colour
If the zone has a specific background, either set ?bg= in the URL to match it, or use ?bg=transparent so the player background shows through. Avoid leaving it as the default if your player adds a white border — this can make the QR harder to scan.
Set widget refresh (optional)
The kiosk page manages its own rotation in JavaScript and never needs a full page reload. You can set the player's refresh interval to something long (e.g. 24 h) or disable it entirely.
Platform compatibility disclaimer
Yodeck is used here as one example of many digital signage platforms on the market. QuuPass provides a standard HTML page and a vanilla iframe embed — we do our best to ensure the output is clean and broadly compatible, but the signage player ultimately controls how the content is rendered. Behaviour such as iframe scaling, transparency handling, and refresh scheduling varies between platforms and can change with player software updates. Your mileage may vary. For platform-specific issues — widget sizing, browser engine limitations, or rendering quirks — please lean on your signage provider's own support resources.
The kiosk draws credentials from the portal's IPSK credential pool. If the pool empties — for example if credentials expire faster than they are refilled — the kiosk shows a spinner and automatically retries every 10 seconds until new credentials are available.
Pool target size
Configure in Portal Settings → Pool tab. A target of 25 credentials is the default. Increase this if you expect many simultaneous guests or if your credential expiry is short.
Top-up strategy
The pool can be topped up by threshold (when it falls below a percentage of the target) or on a schedule. Both modes run automatically — no manual action required.
Credential expiry
Set in Portal Settings → Identity tab. Short expiry (e.g. 4 h) means guests that stay connected will be disconnected more often but pool turnover is faster. Longer expiry (e.g. 24 h) reduces churn but means more concurrent valid credentials in Meraki.
Q: The kiosk displays a spinner instead of a QR code.
A: The credential pool is empty. Check that the portal has an active pool (Portal Settings → Pool tab) and that the pool top-up job has run. The kiosk will recover automatically once credentials are available.
Q: The QR code scans but the device cannot connect.
A: The credential may have just rotated. Ask the guest to scan again. If the problem persists, confirm the SSID is powered up in Meraki and that the RADIUS server is reachable — check the RADIUS Configuration docs.
Q: The kiosk background is white in Yodeck even with ?bg=transparent.
A: Browser transparency in a standalone window means no background is behind the page, so the browser renders white. Use a solid colour matching your Yodeck zone background instead — e.g. ?bg=%232E3331 for the QuuPass dark green. Transparency is most useful when the kiosk is embedded in an iframe over another layer.
Q: The QR code is very small / doesn't fill the zone.
A: The QR scales to 62% of the shorter dimension of the zone. If the zone is very thin (e.g. a sidebar), the QR will be small. Use a square or near-square zone for best results.
Q: The Monitor icon does not appear on a portal card.
A: The Kiosk quick-panel only shows on Mode B portals. Confirm the portal's SSID is using Mode B (IPSK with RADIUS) in Portal Settings → Network tab.