A portal is a branded, guest-facing web page displayed on a tablet or screen at a reception desk, entrance, or common area. Guests self-serve — no staff involvement required.
The portal sits waiting on the device. When a guest approaches, they tap Generate WiFi Credentials. QuuPass generates a unique passphrase and displays it in plain text alongside a scannable QR code. The guest points their phone camera at the QR code and connects instantly. Laptop users can type the passphrase directly into their device Wi-Fi settings.
Credentials are time-limited. After the admin-configured display window expires, the QR code blurs and locks — it cannot be scanned. The passphrase disappears from the screen. The next guest sees an expired state and taps Generate New Credentials to receive their own fresh credential. This ensures every visitor gets a unique credential and previously displayed credentials cannot be reused by anyone who sees the screen after the fact.
Each portal is linked to a specific SSID on a specific Meraki network. A single portal URL can run on any number of screens simultaneously — there is no device limit.
Each portal has its own URL in the format /portal/[tenant-id]/[slug]. You can share this URL via QR code on a printed card, a TV screen, a door sign, or an event badge.
QuuPass is built around the smartphone — the device your visitors already carry. The QR code is the primary connection method: guests point their phone camera at the screen and connect in seconds, no typing required.
For guests on a laptop without a phone, the passphrase is always displayed in plain text alongside the QR code and can be typed directly into laptop Wi-Fi settings. Admins can add custom portal text to guide these guests — for example: “On a laptop? Type the password shown above into your Wi-Fi settings.”
Because a portal can be displayed anywhere — reception, meeting rooms, breakout spaces, printed QR codes on tables — anyone nearby with a phone can approach the nearest screen, tap to generate a credential, and assist another guest. No staff required, no shared password.
From Dashboard → Portals, click New Portal. The wizard guides you through:
The name is for your reference. The slug forms the last part of the public URL — keep it short and URL-safe (e.g. lobby, coworking-a, event-2026). Slugs must be unique within your account.
Select the Meraki network and SSID guests will connect to. The SSID must already be configured for IPSK (Mode A or Mode B). QuuPass shows only eligible SSIDs.
Choose the Meraki group policy that will be applied to every credential issued through this portal. This controls bandwidth, firewall rules, and VLAN assignment for guests.
Set how long each credential remains valid. Options range from 1 hour to 30 days. Credentials are automatically removed from Meraki once they expire.
The Portals page shows all your portals grouped by network. Two view modes are available:
Each portal displayed as a card showing name, SSID, network, active/total credential count, last-used time, expiry duration, group policy, and a live QR code preview. Best for a quick visual overview.
Compact table format for managing many portals at once. Easier to scan names and statuses across a large deployment.
| Action | What it does |
|---|---|
| Enable / Disable | Toggle the portal on or off. A disabled portal still exists but its URL returns a "portal unavailable" page. No new credentials are issued. Existing active credentials remain valid until they expire. |
| Open portal URL | Opens the public guest-facing page in a new tab. Useful for testing the visual appearance or sharing the live link with venue staff. |
| Edit settings | Update portal name, description, slug, expiry duration, group policy, and password display options. Changes take effect on the next visit — already-issued credentials are not affected. |
| Customise branding | Opens the WYSIWYG branding editor. See the Custom Branding documentation for full details. |
| Clean up expired credentials | Removes credentials whose expiry has passed from both QuuPass and the Meraki Dashboard API. Runs automatically on a schedule but can be triggered manually to immediately free IPSK identity slots. |
| Delete portal | Permanently deletes the portal and all credentials associated with it. Credentials are revoked from Meraki immediately. This action cannot be undone. |
The portal edit page lets you update every configuration option set at creation, plus additional fields:
The number of portals and Meraki networks you can connect is determined by your subscription tier. The dashboard header shows your current usage against your plan limit. When you reach the limit, the New Portal button is disabled until you upgrade or free up a slot.