# Common Questions
Source: https://docs.wiacom.ai/access-features/horizon/faq
Technical and compliance questions about Horizon for IT and DPO stakeholders.
## Credential Privacy
**Are end-user home network credentials exposed to the venue, operator, or Wiacom?**
No. The user's home WiFi credentials are never transmitted to or stored by the venue, the operator, or Wiacom. Horizon provisions a dedicated credential set for the user at that venue only. The user's underlying home network details remain entirely within their own equipment. The model is analogous to tokenised payment systems — a venue-specific credential is derived and used without the original ever leaving the user's own environment.
***
## Operational Complexity
**Does Horizon require new hardware or changes to existing infrastructure?**
No. Horizon works alongside existing wireless infrastructure. There is no manual configuration required per user and no changes to the infrastructure beyond the initial controller integration.
***
## Vendor Compatibility
**Will Horizon affect our vendor support status?**
No. Horizon operates through vendor-supported interfaces and does not modify firmware or bypass security controls.
***
## Compliance & Data Protection
**What data does Horizon process?**
Horizon processes the technical identifiers required for provisioning and session management. Personal data captured through an onboarding channel is handled in accordance with the platform's standard data model and the applicable Data Processing Agreement.
For data residency and deployment options see [Platform Overview](/getting-started/platform-overview).
# Overview
Source: https://docs.wiacom.ai/access-features/horizon/overview
Personal WiFi identity orchestration across venues.
Horizon is Wiacom's cloud WiFi identity orchestration layer. It enables personal WiFi experiences across locations — provisioning individual SSIDs or credentials per user and managing their full lifecycle automatically.
Rather than connecting to a shared guest network, each user receives their own named WiFi network provisioned at the venue for the duration of their stay or session.
## How It Works
Horizon is vendor-agnostic and integrates with existing wireless infrastructure — no hardware replacement required. The provisioning method is selected based on what the infrastructure supports.
For environments where direct cloud-to-controller access is not possible, [Wiacom Agent](/integrations/wiacom-agent) can be deployed as a local bridge.
## Use Cases
* Hotel guest personal WiFi for the duration of a stay
* Resident personal SSIDs in serviced apartments
* Temporary personal networks for events or meetings
* Staff and contractor WiFi activated per shift
Contact [info@wiacom.ai](mailto:info@wiacom.ai) for more info or to plan a Horizon deployment.
# Key Access
Source: https://docs.wiacom.ai/access-features/key-access/overview
Shared WPA2 passphrase delivered to registrants by email
Key Access is the base access tier in Wiacom. The venue operator sets a shared WPA2 passphrase for an SSID; Wiacom stores it securely and delivers it to each registered user with a scannable QR code.
Key Access is available for all vendors — with or without an API controller connection.
## How It Works
The venue operator enters a WPA2 passphrase for the location's SSID in Wiacom.
The passphrase is encrypted at rest. For API-connected controllers, Wiacom also pushes it to the SSID automatically.
A user registers through any onboarding channel — Guest Connect, portal, API, etc.
The SSID and passphrase are delivered to the user. The QR code allows one-tap connection on supported devices. These details can optionally be shown on-screen at registration time and sent through one of the enabled communication channels. See [Messaging Services](/integrations/messaging).
The user connects to the SSID using the passphrase in the email.
## Key Access vs WiFi Pass
| | Key Access | WiFi Pass |
| ----------------------- | --------------- | ---------------------------- |
| Credential type | Shared WPA2 PSK | Unique personal PSK per user |
| Controller API required | Optional | Yes for non RADIUS |
| Individually revocable | No | Yes |
| Credential expiry | No | Yes (configurable) |
| Per-user audit trail | No | Yes |
Key Access is ideal for small venues, simple deployments, or as a fallback mode when API connectivity is unavailable. For individual, revocable credentials, upgrade to [WiFi Pass](/access-features/wifi-pass/overview).
## Resilience Mode
For API-connected controllers, Wiacom supports a **static SSID fallback** — the passphrase is stored in Wiacom and delivered by email even if the controller is temporarily unreachable. Guests receive valid credentials regardless of controller availability.
## Updating the Passphrase
Go to **Inventory → Controllers → \[controller] → \[SSID row] → Edit** and enter a new passphrase. For API-connected controllers, Wiacom pushes the change to the SSID immediately.
Changing the shared passphrase disconnects all currently connected devices. All registered users with the old passphrase must reconnect using the new one.
## Vendor Support
Key Access works with any vendor that supports WPA2 Personal (all vendors). For API-connected controllers, Wiacom pushes the passphrase automatically. For legacy/manual deployments, the passphrase is managed in Wiacom and the admin configures the SSID on the device directly.
# Overview
Source: https://docs.wiacom.ai/access-features/overview
How validated users connect to WiFi — Portal, WiFi Pass, Key Access, and Passpoint Connect
Access features define how a registered user receives WiFi connectivity. Once a user has been identified and onboarded through any [onboarding channel](/onboarding/overview), the platform delivers access credentials or a session based on the access features configured for that location.
Onboarding and access are configured independently. The same user can be onboarded through Guest Connect, the captive portal, or an external API — and receive access through any combination of the features below.
## Available Features
Captive portal with a branded splash page. The user registers through an inline WiFi flow and is authenticated via RADIUS. No credential delivery required — access is granted immediately after registration.
A unique personal WPA2 passphrase provisioned per user on the WiFi controller. No shared password — every registrant connects with their own credential, individually revocable and expiry-controlled.
A shared WPA2 passphrase stored securely in Wiacom and delivered to each registered user by email with a scannable QR code. Available for all vendors — with or without an API connection.
Automatic, seamless connection using Hotspot 2.0 profiles. Registered users connect without a password prompt on supported devices — no splash page, no manual credential entry.
Personal SSID provisioned per user — each guest gets their own named WiFi network for the duration of their stay or session. Integrates with PMS, booking apps, and the Wiacom API.
## Choosing a Feature
| Feature | Authentication | Credential per user | Vendor API required | Best for |
| --------------------- | -------------------- | :-----------------: | :------------------: | ------------------------------------------------------- |
| **Portal** | RADIUS (per-session) | — | No | Public guest WiFi, high-volume venues |
| **WiFi Pass** | WPA2 iPSK / RADIUS | ✅ | Yes (or RADIUS) | Venues requiring per-user accountability and revocation |
| **Key Access** | WPA2 PSK | — | No | Simple access delivery to any registered user |
| **Passpoint Connect** | Hotspot 2.0 + RADIUS | ✅ | No | Frictionless returning-user and roaming scenarios |
| **Horizon** | Personal SSID / WPA2 | ✅ | No (agent available) | Hotel stays, residences, personal WiFi per guest |
Multiple features can run simultaneously on the same location using separate SSIDs.
## How Access Delivery Works
After a user completes registration, Wiacom determines which access features are active for the location and delivers accordingly:
* **Portal** — the session is authenticated immediately via RADIUS; the user reaches the internet after completing the splash page flow
* **WiFi Pass** — a personal passphrase and QR code are provisioned on the controller and delivered to the user by email (and optionally shown on-screen)
* **Key Access** — the venue's shared passphrase and QR code are sent to the user by email
* **Passpoint Connect** — a Hotspot 2.0 profile is delivered to the user's device for automatic connection on return visits
See [Messaging Services](/integrations/messaging) for how credentials and notifications are delivered across email, SMS, and other channels.
# Passpoint Connect
Source: https://docs.wiacom.ai/access-features/passpoint-connect/overview
Hotspot 2.0 / Passpoint profile-based automatic WiFi access
Passpoint Connect delivers **automatic WiFi onboarding** using Hotspot 2.0 / Passpoint profiles backed by Wiacom RADIUS infrastructure. Once a device has the profile installed, it connects to Passpoint-enabled SSIDs automatically — no portal redirect, no passphrase entry, no manual SSID selection.
## No API Required
Passpoint Connect does not require a cloud API integration with the WiFi controller. It is configured at the access point level using standard Hotspot 2.0 parameters and Wiacom RADIUS infrastructure — available on all vendors that support Hotspot 2.0.
## How It Works
A Passpoint profile is delivered to the user's device — via OTA provisioning, MDM, or a one-time onboarding flow.
When the device is within range of a Wiacom-enabled Passpoint SSID, it matches the profile automatically.
The Wiacom RADIUS infrastructure authenticates the device using EAP credentials embedded in the profile.
The device is connected — no user interaction required.
## Key Capabilities
* **Automatic WiFi onboarding** — seamless, invisible connection for returning users
* **Profile or certificate-based** — supports EAP-TLS, EAP-TTLS, EAP-PEAP
* **RADIUS-backed** — per-device identity and audit trail
* **Roaming-style access** — consistent experience across multiple locations and venues
* **OpenRoaming-ready** — compatible with WBA OpenRoaming for inter-operator roaming
## Use Cases
| Use case | Description |
| ---------------------------------- | --------------------------------------------------------- |
| **Hotel guest automatic WiFi** | Guest connects on arrival with no portal, no password |
| **Loyalty member recognition** | Returning customers connect automatically |
| **Enterprise MDM-managed devices** | Profiles deployed via MDM; devices auto-connect |
| **Public transit** | Seamless WiFi across a transit network with one profile |
| **OpenRoaming** | Interoperable access across participating global networks |
## Requirements
* Access points with Hotspot 2.0 / IEEE 802.11u support
* Wi-Fi 5 Wave 2 or newer recommended
* Wiacom RADIUS infrastructure (provisioned per region)
* Profile delivery mechanism (OTA, MDM, or Wiacom-managed onboarding)
Contact the Wiacom team at [info@wiacom.ai](mailto:info@wiacom.ai) to plan a Passpoint Connect deployment.
# Overview
Source: https://docs.wiacom.ai/access-features/portal/overview
Captive portal and splash page access control
Portal is Wiacom's captive portal access feature. When a guest connects to an open WiFi SSID, their browser is redirected to a Wiacom-hosted splash page. After completing the onboarding step, Wiacom authenticates the guest via RADIUS using a per-session generated credential — granting internet access.
## Authentication Model
Portal uses **RADIUS authentication with generated per-user credentials**.
When a guest completes the registration form, Wiacom generates a unique encrypted username and password. These are sent to the RADIUS server in a standard Access-Request. The RADIUS server returns an Access-Accept, and the controller grants the guest internet access.
MAC address **may** be used optionally for returning-user recognition or bypass scenarios (for IoT devices, for example), but it is not the default authentication mechanism.Where supported by the vendor, Wiacom can combine MAC identification with an additional secret, such as a suffix or password, instead of relying on simple MAC authentication only.
## How It Works
Guest connects to the open WiFi SSID.
The controller redirects the guest's HTTP traffic to the Wiacom portal URL.
Guest completes the registration form, accepts terms, or logs in via a social provider.
Wiacom sends a RADIUS Access-Request with a generated per-session credential to the RADIUS server.
RADIUS returns Access-Accept; the controller grants the guest internet access for the configured session duration.
## Onboarding Integration
Portal combines onboarding and access in a single inline flow. The form is fully configurable — from a one-click terms acceptance (registration-free, access still tracked by session) to a full registration form with identity and consent capture.
Portal can also work in conjunction with a separate [Guest Connect](/onboarding/guest-connect/overview) page for pre-registration or returning-guest recognition.
## Engagement Features
* **Branded splash pages** — logo, colors, background, copy — fully customizable
* **GDPR consent** — required terms and optional marketing consent
* **AdFlow integration** — inject promotional screens into the registration journey
* **Bandwidth policy** — per-guest limits applied via RADIUS reply attributes
* **Session timeouts** — configurable per location
## Technical Notes
* The SSID must be **open** (no WPA2) to allow captive portal redirect
* Wiacom RADIUS infrastructure authenticates each session using auto-generated per-user credentials
* A **walled garden** (pre-authentication allow-list) must be configured on the controller
* RADIUS server addresses and portal redirect URLs are region-specific — obtain from the Wiacom admin panel or the Wiacom team
## Vendor Support
| Vendor | Portal | Integration mode |
| -------------- | ------ | -------------------- |
| Cisco Meraki | ✅ | API or legacy/manual |
| Aruba | ✅ | Legacy/manual |
| Ruckus | ✅ | Legacy/manual |
| UniFi | ✅ | API |
| Cambium | ✅ | Legacy/manual |
| Fortinet | ✅ | Legacy/manual |
| TP-Link Omada | ✅ | Legacy/manual |
| MikroTik | ✅ | Legacy/manual |
| Huawei AC/AP | ✅ | Legacy/manual |
| Draytek Vigor | ✅ | Legacy/manual |
| Teltonika RUTX | ✅ | Legacy/manual |
| Cisco WLC | ✅ | Legacy/manual |
For the full vendor compatibility table, see [Supported WiFi Vendors](/wifi-vendors/index).
Configure Portal for your location — forms, appearance, and session settings
# Setting up Portal
Source: https://docs.wiacom.ai/access-features/portal/setting-up
Configure Portal for your venue location
Portal is available by default on every location. Configuration can be pre-set by the Wiacom admin at location creation, or adjusted at any time from the client dashboard.
## Client dashboard configuration
Portal appearance, registration methods, session rules, and data collection fields are all configured from the **Location Settings** section of the client dashboard. See [Location Settings — Captive Portal Settings](/client-reference/location-settings) for the full reference.
## Splash page and Captive Network Assistant
The Portal splash page is the web page shown to the user after connecting to the captive WiFi SSID. It runs either inside the device's **Captive Network Assistant (CNA)** or in a standard browser.
**Captive Network Assistant (CNA)** it is a small restricted browser opened automatically by operating systems such as iOS, macOS, Android when they detect that WiFi access requires authentication. It is not a full browser and may have limitations for tabs, downloads, cookies, JavaScript behavior, payment redirects, and external app opening.
Wiacom Portal is optimized to work inside CNA environments. The splash page focuses on the essential onboarding steps required to identify the user, collect consent, complete registration, and release internet access.
Typical CNA flow:
1. User connects to the Portal SSID
2. The device detects captive portal access
3. The Wiacom splash page opens automatically in the CNA window
4. The user completes the configured onboarding method
5. Wiacom authenticates the session through the configured network integration
6. Internet access is granted
Depending on the portal configuration, the splash page may include:
* Terms and conditions acceptance
* Email registration
* Phone number and PIN/OTP verification
* Voucher code access
* Social login
* Paid access plan selection - with limitations due to CNA behavior
* Marketing consent
* Data collection fields
* Thank-you or welcome-back page
Because CNA behavior differs between operating systems and device vendors, some advanced flows may continue in the user's default browser when required. For example, payment pages, external identity providers, or app-based redirects may work better outside the CNA window.
## Connecting your WiFi equipment
The SSID must be configured for captive portal redirect on your device. Follow the guide for your vendor:
* [Cisco Meraki — Portal](/wifi-vendors/cisco-meraki/portal)
* [Aruba — Onboarding](/wifi-vendors/aruba/onboarding)
* [Ruckus — Onboarding](/wifi-vendors/ruckus/onboarding)
* [UniFi — Onboarding](/wifi-vendors/unifi/onboarding)
* [MikroTik — Onboarding](/wifi-vendors/mikrotik/onboarding)
* [Huawei AC/AP — Onboarding](/wifi-vendors/huawei/onboarding)
* [Draytek Vigor — Onboarding](/wifi-vendors/draytek/onboarding)
* [Teltonika RUTX — Onboarding](/wifi-vendors/teltonika/onboarding)
For the full vendor compatibility table, see [Supported WiFi Vendors](/wifi-vendors/index).
For API-connected controllers, Wiacom pushes the portal URL and authentication settings to the SSID automatically. For legacy or manual devices, the Wiacom admin provides the server details and portal URL to configure directly on the device.
For large deployments, Wiacom Auto-Provisioning is available.
Wiacom AP Auto-Provisioning automatically registers new or replaced access points when they contact the Wiacom platform for the first time. Instead of requiring an administrator to manually add the AP in the admin panel, Wiacom detects the device from the first captive portal request and creates the AP record automatically using its internal matching logic.
## Walled garden
Guests must be able to reach the portal before authenticating. Add the following to your device's pre-authentication allow-list:
| Category | Domains |
| -------------------- | ---------------------------------------------------------------------------------------------------- |
| **Required** | `*.wiacom.ai` |
| Facebook / Instagram | `*.facebook.com`, `*.fbcdn.net`, `*.akamaihd.net`, `connect.facebook.net`, `*.instagram.com` |
| Google | `*.google.com`, `*.googleapis.com`, `*.gstatic.com` |
| Twitter / X | `*.twitter.com`, `*.twimg.com` |
| LinkedIn | `*.linkedin.com`, `*.licdn.net`, `*.licdn.com` |
| CDN | `*.akamaitechnologies.com`, `*.akamaiedge.net`, `*.akamaized.net`, `*.amazonaws.com`, `*.fastly.net` |
Only add the social provider domains for the login methods you have enabled on your portal. See your vendor's onboarding guide for how to apply the walled garden on your specific hardware.
## Testing
1. Connect a device to the Portal SSID
2. The captive portal splash page will open automatically
3. Complete the registration flow
4. Verify internet access is granted after registration
If the portal does not open automatically, navigate to any plain HTTP address in your browser to trigger the captive portal redirect. Some devices browse HTTPS-only by default and may not detect the portal without an explicit HTTP request.
# Enabling WiFi Pass
Source: https://docs.wiacom.ai/access-features/wifi-pass/enabling
Activate and configure WiFi Pass on a Wiacom location
## Prerequisites
* A Wiacom location with an API-connected controller
* At least one SSID assigned the **WiFi Pass** role on the controller
* WiFi Pass activated on your Wiacom plan
## Steps
Go to **Locations** → select your location → **WiFi Pass → Enable**.
Under **WiFi Pass → Settings**:
| Mode | Description |
| ------------- | --------------------------------------------------------------------------------------- |
| **Instant** | Passphrase created on registration, shown on the thank-you page and emailed immediately |
| **Confirmed** | User confirms their email first; passphrase sent in a follow-up email |
Under **WiFi Pass → Expiry**:
| Option | Detail |
| ------------------ | ----------------------------------------------- |
| **No expiry** | Passphrases never expire (default) |
| **Fixed period** | Expires N days after provisioning |
| **Rolling period** | Expires N days after the user's last connection |
WiFi controllers do not natively enforce PSK expiry. Wiacom enforces expiry by revoking credentials on the controller on an hourly schedule.
Go to **WiFi Pass → Email**. In Confirmed mode, configure both emails: the confirmation request and the credential delivery.
1. Register via your onboarding channel (Guest Connect URL, portal, etc.)
2. Verify the credential delivery email arrives with passphrase and QR code
3. Connect a device using the personal passphrase
4. Confirm the credential appears in **WiFi Pass → Credentials**
## Managing Credentials
Go to **WiFi Pass → Credentials**:
| Action | Effect |
| -------------- | --------------------------------------------------- |
| **Suspend** | Immediately revoked on the controller; restorable |
| **Restore** | Re-activates a suspended credential |
| **Delete** | Permanently removed from Wiacom and the controller |
| **Expire now** | Forces immediate expiry outside the scheduled cycle |
Select multiple credentials for bulk **Suspend**, **Delete**, or **Export** as CSV.
# Overview
Source: https://docs.wiacom.ai/access-features/wifi-pass/overview
Per-user personal passphrase (iPSK/MPSK/DPSK/other) provisioning
WiFi Pass provisions a **unique personal WiFi passphrase** for each registered user. Each person gets their own Identity (Uniques PSK) provisioned directly on the WiFi controller via the vendor API — eliminating the shared password model entirely.
**For set-up without RADIUS** — requires a cloud API connection to the controller or an agent [provided by Wiacom](/integrations/wiacom-agent). Wiacom provisions credentials directly via the vendor API.
**For set-up with RADIUS** — the RADIUS server handles per-user PSK lookup. API access to the controller is desired for initial configuration but is not required for ongoing credential management.
## Why WiFi Pass?
Every user gets their own passphrase — no sharing, no circulation
Revoke a single user's access without affecting anyone else
Passphrases expire after a configurable period and are renewed on re-registration
Every connection is tied to a known, consented registered user
## How It Works
User registers through any configured onboarding channel (Guest Connect, portal, API, PMS, App, online resource).
Wiacom creates a unique PSK on the WiFi AP/controller.
The SSID, unique passphrase, and connection QR code are generated and delivered to the user. The QR code allows one-tap connection on supported devices. These details can optionally be shown on-screen at registration time and sent through one of the enabled communication channels. See [Messaging Services](/integrations/messaging).
User connects using standard WPA2 — no app, no profile, no special client required.
Access is revocable and expiry-controlled from the Wiacom dashboard at any time.
## Provisioning Modes
| Mode | Behaviour |
| ------------- | ------------------------------------------------------------------------------------------------- |
| **Instant** | Connection details created on registration, shown on the thank-you page and delivered immediately |
| **Confirmed** | User clicks a confirmation link first; details delivered after verification |
Confirmed mode validates provided registration details before issuing a credential — recommended for public-facing deployments.
## RADIUS Variant
For deployments exceeding vendor unique PSK's limits, Wiacom supports \*\* Unique PSK with RADIUS\*\* mode. The SSID is configured with Wiacom RADIUS server details, and the RADIUS server performs per-user PSK lookup. Credential management remains entirely within Wiacom — the controller's native API or [Wiacom agent](/integrations/wiacom-agent) is not used in this path.
## Vendor Support
WiFi Pass without RADIUS requires capable wifi infrastructure, an API-connected controller or Wiacom agent.
| Vendor | WiFi Pass support |
| ------------ | -------------------------------------------------------------------------- |
| Cisco Meraki | ✅ Full (up to 5,000 iPSKs per SSID; RADIUS variant for larger deployments) |
| Aruba | Coming soon |
| Ruckus | Coming soon |
| UniFi | Coming soon |
| Cambium | Coming soon |
## Next Steps
Hardware and firmware requirements by vendor
Activate and configure WiFi Pass on a location
# Requirements
Source: https://docs.wiacom.ai/access-features/wifi-pass/requirements
Hardware and firmware requirements for WiFi Pass
WiFi Pass requires an API-connected controller. The vendor must support Identity PSK (iPSK) or MPSK provisioning via their cloud API.
## Controller Support Matrix
| Vendor | Unique PSK Support | Minimum Firmware | Max Unique PSKs per SSID |
| ---------------- | ------------------ | ------------------ | ------------------------ |
| **Cisco Meraki** | ✅ | MR 30.1+ | 5,000 |
| **Aruba** | Planned | ArubaOS 8.4+ | Varies |
| **Ruckus** | Planned | SmartZone 5.1+ | Varies |
| **UniFi** | Planned | UniFi Network 7.x+ | Varies |
| **Cambium** | Planned | cnMaestro 3.x+ | Varies |
For deployments exceeding the per-SSID iPSK limit, Wiacom supports iPSK-with-RADIUS mode. Contact the Wiacom team to enable this for your location.
## Client Device Compatibility
Identity PSK uses standard WPA2 authentication — guests enter the passphrase like any other WiFi password. No app, profile, or special client is required.
| Platform | Minimum Version |
| -------- | --------------- |
| iOS | 14+ |
| Android | 9+ |
| macOS | 10.15+ |
| Windows | 10+ |
| ChromeOS | 88+ |
# Controllers
Source: https://docs.wiacom.ai/admin-reference/controllers
Manage API-connected WiFi controllers in Wiacom
Controllers are API-connected WiFi vendor integrations. Each controller represents a connection to a single vendor organisation or management instance.
## Controller Status
| Status | Meaning |
| ------------ | ----------------------------------------- |
| **Active** | Connected and operational |
| **Syncing** | Topology sync in progress |
| **Warning** | Configuration issues require attention |
| **Error** | API connection failed — check credentials |
| **Disabled** | Manually disabled |
## Adding a Controller
Go to **Inventory → Controllers → Add controller**, select your vendor, and follow the vendor setup guide:
* [Cisco Meraki — Onboarding](/wifi-vendors/cisco-meraki/onboarding)
## Removing a Controller
1. **Inventory → Controllers → \[controller] → Settings → Remove controller**
2. Confirm removal
Removing a controller does not delete guest registrations, credentials, or analytics data. No changes are pushed to the physical equipment.
## API Credential Rotation
1. **\[Controller] → Edit credentials**
2. Paste the new API key and click **Validate and save**
No guest access is interrupted during rotation.
## Sync Behaviour
Automatic background syncs run every 6 hours. Trigger a manual sync via **Sync from controller**.
**A sync does:**
* Add new SSIDs, update SSID metadata, remove deleted SSIDs
* Refresh the AP inventory
**A sync does not:**
* Overwrite Wiacom role assignments (Portal / WiFi Pass / Key Access)
* Overwrite location mappings
* Push config changes to the controller
* Modify or delete guest credentials
# Inventory
Source: https://docs.wiacom.ai/admin-reference/inventory
Managing routers, access points, and controllers in Wiacom
The Inventory section manages all WiFi equipment connected to Wiacom — individual routers and access points (legacy mode) and cloud controller connections (API mode).
## Routers — Individual Devices (Legacy Mode)
### Adding a Single Device
1. Go to **Inventory → Routers → Add New Router**
2. Select the **Router Vendor** from the dropdown
3. Fill in the required fields (typically WAN MAC address or NAS-ID — varies by vendor)
4. Optionally assign a **Location** to associate the device immediately
5. Click **Save**
### Bulk Import
For deployments of 10 or more devices:
1. Go to **Inventory → Routers → Unallocated Routers → Import from Excel**
2. Click **Download import template** for vendor-specific column headers
3. Fill in the template (contact Wiacom for vendor-specific field requirements)
4. Select the **Router Vendor** and optionally a **Location**
5. Upload the file and click **Import Router**
For large deployments where one controller manages multiple sites, split imports by site and select the corresponding Wiacom location for each import run.
### Unallocated Devices
Devices added without a location appear under **Inventory → Routers → Unallocated Routers** and can be assigned to locations at any time.
## Controllers — API Integrations
API-connected controllers are managed under **Inventory → Controllers**. See [Controllers](/admin-reference/controllers) for full details.
# Locations
Source: https://docs.wiacom.ai/admin-reference/locations
Manage venue locations in Wiacom
A **Location** represents a single physical venue. Each location has its own registration page, credentials, portal splash page, analytics, and guest database.
Hierarchy: **Access Points → Zones → Location → Customer account**. A location belongs to exactly one business name (data protection requirement).
## Creating a Location
1. Go to **Locations → Add location**
2. Enter name, address, and timezone
3. Click **Save**
Guest Connect, WiFi Pass, and Portal are available for configuration from the location page. Portal is available by default; configuration options are accessible both from the admin side at location creation and from the client portal afterwards.
## Location Settings
| Setting | Description |
| ------------ | ------------------------------------------------ |
| **Name** | Display name in admin and guest emails |
| **Address** | Physical address for analytics and MSP filtering |
| **Timezone** | Used for analytics and session expiry |
| **Slug** | URL identifier for the Guest Connect page |
| **Tags** | Custom tags for multi-location grouping |
Changing the slug breaks existing QR codes and published links.
## Multi-Location and MSP
* All locations visible from the top-level **Locations** view
* Tag locations by region, brand, or client for grouped views and analytics
* MSP admins manage multiple customer accounts from a single login
## Deleting a Location
Deleting a location permanently removes all guest registrations, consent records, and analytics. This cannot be undone.
1. Location settings → **Danger zone → Delete location**
2. Type the location name to confirm
# Ad Serve
Source: https://docs.wiacom.ai/client-reference/ad-serve
Programmatic ad serving through the captive portal — manage advertisers, campaigns, creatives, and Portal Ad Flow rules.
**Ad Serve is an optional feature.** This menu is visible only on accounts where Ad Serve has been enabled. Contact [info@wiacom.ai](mailto:info@wiacom.ai) to enable it.
The **Ad Serve** menu contains two sub-systems — the full Ad Service module and Portal Ad Flow Rules — depending on your account configuration.
## Ad Service
The full Ad Service module enables venue operators and MSPs to run structured advertising campaigns through the captive portal. It is organised as a standard ad management workflow:
### Advertisers
Manage advertiser accounts. Each advertiser has a name, contact details, and billing configuration. Campaigns and creatives are associated with an advertiser.
### Campaigns
Create and manage ad campaigns. Each campaign is linked to an advertiser and defines:
* Campaign name and active date range
* Targeting rules (location, audience segment, time of day)
* Budget or impression cap
* Associated creatives
### Creatives
Upload and manage ad creative assets used in campaigns — static images, animated GIFs, or HTML banners. Each creative has dimensions, format, and a destination URL for click-through.
### Audience Report
Performance dashboard for all active and completed campaigns. Shows impressions, clicks, and click-through rate (CTR) broken down by campaign, location, date, and creative.
### Embed Generator
Generates embed codes for placing Wiacom ad units in external contexts — for example, embedding a campaign unit into a third-party website or digital signage system.
***
## Portal Ad Flow Rules
Portal Ad Flow Rules inject ad interstitial screens into the captive portal guest journey at configurable points — for example, between the welcome screen and the login form, or on the thank-you page.
Each rule defines:
* Which portal screen triggers the interstitial
* The creative to display (image, video, or HTML)
* A countdown timer duration after which the guest is auto-redirected
* Whether the guest can skip the ad before the timer expires
* Branding overrides (colours, logo, font) for the interstitial page
For full configuration details see the Portal Ad Flow Rules documentation linked from within the Ad Serve menu.
# Advanced Campaigns
Source: https://docs.wiacom.ai/client-reference/campaigns/advanced-campaigns
Scheduled bulk SMS and email campaigns with full audience segmentation — three-step wizard.
**Advanced Campaigns** is the full campaign builder. It supports both SMS and email channels, rich audience segmentation, and scheduled delivery. Campaigns are built through a three-step wizard.
## Step 1 — General information
### Channel selection
| Checkbox | Effect |
| ------------------------ | -------------------------------------------------------------- |
| **Send SMS campaign** | Enables the SMS channel. Shows the estimated SMS credit count. |
| **Send E-MAIL campaign** | Enables the email channel. Shows the estimated email count. |
Both channels can be active simultaneously in a single campaign.
### Scheduling
Set the **Send the campaign at** datetime using the date and time picker. Leave blank to send immediately on submission.
### Global filters
| Filter | Notes |
| ----------------------- | ------------------------------------------------------------------------- |
| Sender | SMS sender name — maximum 11 characters |
| Send campaign to | Contact segment: All contacts, or active within a specific recency window |
| Filter by gender | All / Male / Female |
| User anniversary period | Target guests with a birthday or anniversary in a specific interval |
| Filter by name | Target a specific named guest |
| Location | One or multiple locations |
### Technical filters
An expandable section for advanced segment logic. Contact Wiacom support for available technical filter options on your account.
## Step 2 — Campaign message
**SMS:** text area with a live character counter. At 161 or more characters the message is split into a second SMS — cost doubles. Special characters may consume additional character budget depending on the GSM character set.
**Email:** rich-text composer available when the email channel is active. Use the [Email Template Builder](/client-reference/campaigns/email-template-builder) to create and reuse branded templates.
## Step 3 — Summary & confirm
A plain-text summary shows the final recipient count: "SMS Campaign: the message will be sent to N recipients according to selected filters."
Review the count before submitting. Click **Submit** to schedule or send. Click **Previous step** to go back and adjust filters or message content.
Once submitted, a campaign cannot be recalled if the send time has already passed. For scheduled campaigns, you can still edit or cancel from the [Campaigns report](/client-reference/stats/campaigns-report) before the send time.
# Email Template Builder
Source: https://docs.wiacom.ai/client-reference/campaigns/email-template-builder
Visual drag-and-drop email composer for creating reusable branded campaign templates.
The **Email Template Builder** is a visual drag-and-drop composer for building reusable HTML email templates. It opens in a new browser tab.
## What it is for
Templates created here are available as starting points when composing the email content in Step 2 of the [Advanced Campaigns](/client-reference/campaigns/advanced-campaigns) wizard. Using a template ensures brand consistency across all outbound emails — logo placement, colours, fonts, and footer copy are applied automatically.
## Working with templates
**Creating a template** — click **New template**, give it a name, and use the drag-and-drop editor to build the layout. Add content blocks (image, text, button, divider, spacer), set colours and fonts, and save.
**Editing a template** — select an existing template from the list, make changes, and save. Edits apply to future campaigns; already-sent campaigns are not affected.
**Deleting a template** — select a template and click Delete. This cannot be undone. Any campaign currently using this template as a base will not be affected — the template content was copied at the time the campaign was created.
Build at minimum one default template that matches your venue branding before running your first email campaign. A consistent template improves open rates and guest recognition.
# Live Campaigns
Source: https://docs.wiacom.ai/client-reference/campaigns/live-campaigns
Event-triggered campaigns that fire automatically when a guest connects to or disconnects from WiFi.
**Live Campaigns** run in real time. They fire automatically on guest connect or disconnect events — no manual scheduling or intervention required once the campaign is active.
## Campaign types
| Type | Behaviour |
| -------------- | ----------------------------------------------------------------------------- |
| **On Event** | Fires on every connect or disconnect event, for every eligible guest |
| **One Time** | Fires once only — on the guest's very first connection across all time |
| **Once a Day** | Fires once per calendar day regardless of how many times the guest reconnects |
## Configuration fields
### Campaign identity
| Field | Notes |
| ------------------------------ | ---------------------------------------------------- |
| Campaign name | Internal reference label |
| Start date / Stop date | Calendar dates when the campaign is active |
| Start hour / Stop hour (daily) | Active time window within each day, e.g. 08:00–22:00 |
### Audience filters
| Field | Notes |
| --------------------- | ------------------------------------------------------------------------ |
| Age range | Filter by guest age band |
| Gender | All / Male / Female |
| Anniversary period | Target guests with a birthday or custom anniversary in the active window |
| Filter by name | Target a specific named guest |
| Customer visits (max) | Only trigger for guests who have visited at least N times |
### Trigger settings
| Field | Notes |
| -------------------------------- | ----------------------------------------------------------------------- |
| Message on connect | Yes / No — whether to send a message at connection time |
| Message on disconnect | Yes / No — whether to send a message at disconnection time |
| Delay after connect (seconds) | How many seconds after the guest connects before the message is sent |
| Delay after disconnect (seconds) | How many seconds after the guest disconnects before the message is sent |
### Location & equipment selection
Choose which locations and APs this campaign applies to. All locations and APs are selected by default. Deselect specific APs to restrict the campaign to certain areas within a venue.
### Message fields
Two text areas — **Message on connect** and **Message on disconnect** — each with a live character counter. Maximum 160 characters per message to avoid double-SMS cost.
## Campaign history
The bottom of the Live Campaigns page shows the last active campaigns in a table with name, type, schedule, and status.
Use **Once a Day** with a short welcome message to greet returning regulars without overwhelming frequent visitors. Use **One Time** for onboarding messages — for example, instructions on how to use the venue's loyalty app.
# Remarketing Campaigns
Source: https://docs.wiacom.ai/client-reference/campaigns/remarketing-campaigns
Build hashed audience lists from your registered WiFi guests for import into Meta (Facebook/Instagram) advertising platforms.
**Remarketing Campaigns** turns your registered WiFi audience into targetable Custom Audiences on Meta advertising platforms. The feature generates hashed contact exports formatted for direct import into Meta Ads Manager — no raw personal data is ever included in the output file.
Only guests who have given explicit marketing consent are included in any export. This is enforced by the platform and cannot be overridden.
## Two export modes
The mode is selected via the **Remarketing Campaign Audience** checkbox:
| Mode | Checkbox state | What it produces | Use case |
| --------------------- | -------------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------- |
| **Facebook Audience** | Unchecked | Hashed phones · hashed emails · Facebook IDs | Upload as a Custom Audience in Meta Ads Manager for targeting or lookalike generation |
| **Facebook Events** | Checked | Same identifiers + Event Name + Event Time | Upload as a Conversion Event audience — matches guests to a specific event for attribution or retargeting |
When **Facebook Events** mode is active, two additional required fields appear:
| Field | Description |
| -------------- | ------------------------------------------------------------------------------- |
| **Event Name** | The Meta internal event identifier (e.g. `Purchase`, `ViewContent`, `Lead`) |
| **Event Time** | The datetime of the event, matching Meta's `event_time` parameter specification |
## Audience filters
All filters update a live counter bar in real time. The counter shows matched contacts broken down by identifier type:
| Badge | What it counts |
| ------------------------ | ------------------------------------------------ |
| 📞 Phones (green) | Matched contacts with a verified phone number |
| ✉️ Emails (blue) | Matched contacts with an email address |
| Facebook IDs (dark blue) | Matched contacts with a Facebook login |
| Total (grey) | All matched contacts across all identifier types |
### Available filters
| Filter | Notes |
| ------------------------------- | -------------------------------------------------------- |
| Campaign name | Internal label for this export — required |
| Gender | All / Male / Female |
| Language | All or a specific portal language |
| Name | Filter by a specific guest name |
| Birthday / anniversary interval | Target guests with an anniversary in a given date window |
| All ages (checkbox) | Checked by default — bypasses the age range filter |
| Age range | Slider 18–100, active only when All ages is unchecked |
| Last visit interval | Only include guests last seen within this date range |
| Visit count | Only include guests with at least N connections |
| Locations | Checkboxes — all locations selected by default |
## Exporting the audience
The export buttons are disabled until the form passes validation and at least one matching contact is found.
Remarketing exports require a verified operator contact — a phone number or email address that has been provisioned and approved through your organisation's data protection process, typically provided by your Data Protection Officer (DPO). This contact is separate from general account details and is used solely to authorise data export operations. If no approved contact is on file, the export will be disabled. Contact your Wiacom account administrator to arrange provisioning.
Two export actions are available:
**Download BI Data** — generates and downloads a CSV immediately. Contains hashed identifiers formatted to Meta's Custom Audience specification (SHA-256, normalised per Meta's requirements).
**Export contacts** — queues the export via the **Download Manager** section. Useful for large audiences. The file appears in the Download Manager when ready.
## Campaign history
The bottom of the page shows the last 10 exports:
| Column | Description |
| ------------- | ------------------------------------------------------- |
| Name | Campaign name |
| Type | `Facebook Audience` or `Facebook Events` |
| Date | Export timestamp |
| Authorization | Verified operator contact used to authorise this export |
## GDPR note
All remarketing exports are scoped exclusively to guests who have given marketing consent — this is applied automatically by the platform. The hashed format satisfies Meta's technical upload requirement. The underlying legal obligation to maintain a valid consent basis for processing remains with the data controller.
# SMS Calculator
Source: https://docs.wiacom.ai/client-reference/campaigns/sms-calculator
Calculate how many SMS segments your message will consume and the estimated send cost before launching a campaign.
The **SMS Calculator** is a utility tool for composing SMS messages without inadvertently triggering multi-segment billing.
## How to use it
Type or paste your message text into the text area. The calculator updates in real time showing:
| Output | Description |
| ------------------------ | --------------------------------------------------------- |
| **Character count** | Current number of characters in the message |
| **Characters remaining** | Characters left before the next SMS segment is created |
| **SMS segments** | How many individual SMS messages this content will create |
| **Estimated cost** | Total cost at your account's current per-SMS rate |
## SMS segment rules
A standard SMS is 160 characters using the GSM-7 character set. If your message contains any character outside the GSM-7 set (for example, certain accented characters, emoji, or smart quotes), the encoding switches to Unicode (UCS-2) and the per-segment limit drops to 70 characters.
For multi-segment messages, each segment has a slightly lower character limit because some characters are reserved for the concatenation header:
| Encoding | Single SMS | Each segment in a multi-SMS |
| --------------- | -------------- | --------------------------- |
| GSM-7 | 160 characters | 153 characters |
| Unicode (UCS-2) | 70 characters | 67 characters |
A message that is 161 characters in GSM-7 encoding will be billed as **2 SMS messages** for every recipient. Always check the segment count before scheduling a bulk campaign.
Use the SMS Calculator to finalise your message content before pasting it into the [Advanced Campaigns](/client-reference/campaigns/advanced-campaigns) or [Live Campaigns](/client-reference/campaigns/live-campaigns) composer.
# Control Panel
Source: https://docs.wiacom.ai/client-reference/control-panel
The home screen after login — live counters, charts, equipment status, and quick campaign tools.
Log in to your Wiacom dashboard using the credentials provided by your account administrator.
## Live counters
Four numbers at the top of the page update in real time:
| Counter | What it means |
| --------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **Online** | Devices currently connected at the network layer to any AP in the account |
| **Active users** | Users with a live Wiacom session — completed registration and granted access |
| **Total interaction** | Unique devices that have opened the captive portal in the current period |
| **Marketing consent** | Opt-in rate shown as a donut chart. Displays a **Fully GDPR compliant** badge when all consent records are in order |
**Online ≠ Active.** A device can be connected (online) without having registered. Only users who completed a registration flow count as Active.
## Charts
**Last 7 days (hourly)** — bar chart of connections by hour of day across the past week. Use this to identify peak arrival windows and plan staffing accordingly.
**Last 30 days (daily)** — bar chart of registrations per day. Below it, a two-bar comparison shows **First visit %** vs **Returns %** — your repeat-visitor loyalty rate at a glance.
## Financial & Campaign status widget
Two tabs in the bottom-left panel of the control panel.
**Credit tab** shows:
* Current credit balance, currency, and billing type (prepaid / postpaid)
* SMS cost per message
* Email cost per message
* Routing type
**Campaign tab** shows the last 5 campaigns with name, location tag, send datetime, and a status badge — `Sent`, `Programmed`, or `0 Contacts`.
## Equipment status widget
Lists every registered AP grouped by location. Each entry shows:
| Field | Description |
| ------------------------- | ------------------------------------------------------------------------------------ |
| Location name | Venue name and address |
| In roaming with N routers | Number of APs under this location |
| Login method badges | Colour-coded counts by method (LinkedIn, Instagram, Twitter, Facebook, phone, email) |
| Router tag + MAC | Hardware identifier |
| Status icon | 👍 online · 👎 offline or monitoring not supported for this hardware |
Real-time status monitoring (👍 / 👎) is only available for supported hardware models. A 👎 icon does not necessarily mean the equipment is offline — it may mean real-time heartbeat is not supported for that model.
## Quick campaign panel
A shortcut to send an SMS without going through the full campaign wizard. Three tabs across the top:
### SMS Campaign
Send a bulk SMS to a filtered segment of your audience.
| Field | Notes |
| ---------------- | ------------------------------------------------------------------------------------ |
| Campaign name | Internal reference |
| Location | Single location or all locations |
| Send campaign to | All contacts / Online now / Active in the last 7, 10, 15, or 30 days |
| Send campaign at | Leave blank to send immediately, or pick a future date and time |
| Sender | Your brand name as it appears on the SMS. Maximum **11 characters** |
| Message | Maximum **160 characters**. Exceeding this creates a second SMS and doubles the cost |
### SMS (single recipient)
Send a one-off SMS to a specific phone number. Enter the number, sender name, and message text, then click **Send**.
### Block number
Look up a phone number and **Block** or **Release** it from receiving campaign messages. Blocking prevents promotional SMS delivery only — it does not affect active WiFi sessions or valid OTP codes.
# Paid Plans
Source: https://docs.wiacom.ai/client-reference/data-plans/paid-plans
Fee-based WiFi access tiers — customer-specific development on request.
**Customer-specific feature.** Paid Plans is a custom development module built on request for specific client deployments. It is not available on standard Wiacom accounts.
If your use case requires fee-based WiFi access tiers, payment gateway integration, or monetised access flows, contact [info@wiacom.ai](mailto:info@wiacom.ai) to discuss your requirements.
# Vouchers
Source: https://docs.wiacom.ai/client-reference/data-plans/vouchers
Issue prepaid, free, promotional, or limited-use WiFi access codes for captive portal environments.
**Vouchers** is a controlled-access feature for captive portal environments. It allows an admin or venue operator to create access code plans and generate individual codes that guests enter at the portal login screen to gain WiFi access — no phone number or social login required.
The system has two layers: **Plans** (the rules template) and **Codes** (individual access codes generated from a plan).
## Creating a plan
Navigate to **Data Plans → Vouchers** and click **New Plan**.
### Access rules
| Setting | Description |
| -------------------- | --------------------------------------------------------------------------------------------------------- |
| Plan name | Internal label — e.g. "Coffee purchase 2hr", "Conference day pass", "Free 30min" |
| Location | Which venue this plan belongs to |
| Validity period | Number of days the code remains valid from first use |
| Session duration | How long a single WiFi session lasts — e.g. 2 hours, 1 day |
| Download speed limit | Maximum download bandwidth per session (leave blank for unlimited) |
| Upload speed limit | Maximum upload bandwidth per session (leave blank for unlimited) |
| Traffic quota | Total data allowed per code in MB or GB (leave blank for unlimited) |
| Device limit | Maximum number of devices that can use this code |
| Device binding | When ON, the code is permanently bound to the first device that uses it — subsequent devices are rejected |
### Branding
| Setting | Description |
| --------------- | -------------------------------------------------------------------------------- |
| Logo | Displayed on the printable voucher output |
| Voucher message | Custom text shown on the voucher — e.g. "Thank you for dining with us" |
| CTA link | Optional button on the printed voucher — e.g. "Visit our menu" with a URL |
| QR preview | Toggle to include a scannable QR code of the access code on the printable output |
## Generating codes
Once a plan is saved:
1. Open the plan and click **Generate codes**.
2. Enter the number of codes to generate.
3. Click **Generate**. Wiacom creates unique alphanumeric codes attached to this plan's rules.
4. Export the codes as **Excel** or **PDF**.
The PDF export formats each code as a printable voucher card — plain text code, QR code, plan name, validity, and any configured branding.
## Guest flow at the portal
Guest connects to the WiFi SSID. The captive portal opens.
Guest selects **Voucher / Access Code** from the available login options.
Guest enters the code from their printed voucher or digital delivery.
The platform checks: code exists · plan is active · code not expired · device limit not exceeded · quota not exhausted · session rules are valid.
If all checks pass, WiFi access is granted through the captive portal flow.
## Tracking code status
The code list shows every generated code with its current state:
| Status | Meaning |
| ------------- | ------------------------------------------------- |
| **Active** | Valid — not yet used |
| **In use** | Used at least once and within the validity window |
| **Exhausted** | Device limit or traffic quota reached |
| **Expired** | Validity period has passed |
| **Revoked** | Manually deactivated by an admin |
**Code list columns:** Code · Plan · Location · Status · First used · Device count · Data used · Expires at · Actions
## Revoking a code
Click the **Revoke** action on any code to immediately deactivate it. A revoked code is rejected at the portal with an invalid code error. This action cannot be undone — if access needs to be restored, generate a new code from the same plan.
## Export formats
| Format | Contents |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Excel** | One row per code — code value, plan, location, status, expiry date. Suitable for mail-merge or bulk distribution. |
| **PDF** | One printable voucher card per code with QR code, branding, and usage instructions. Suitable for printing and physical distribution. |
# Download Manager
Source: https://docs.wiacom.ai/client-reference/download-manager
Access generated export files — PDF reports, voucher exports, and campaign data — ready for download.
The **Download Manager** is always visible in the navigation. It stores generated export files that are ready for download.
## What appears here
Files are added to the Download Manager automatically when an export is queued asynchronously — for example:
* [Traffic Analytics PDF reports](/client-reference/stats/traffic-analytics) generated via the Export button
* [Remarketing Campaign](/client-reference/campaigns/remarketing-campaigns) exports queued via the **Export contacts** button
* [Voucher](/client-reference/data-plans/vouchers) PDF and Excel exports for large code batches
Small exports (such as voucher CSVs with few codes) may download immediately rather than appearing here.
## Managing files
| Action | Description |
| ------------ | -------------------------------------------------------------------- |
| **Download** | Click the file name or download icon to save the file to your device |
| **Delete** | Remove a file from the list once it is no longer needed |
Files remain available in the Download Manager for a limited period after generation. The exact retention window depends on your account configuration.
If a generated report is not appearing here after a few minutes, try refreshing the page. For large PDF reports covering many locations or a long date range, generation may take longer than usual.
# Location Settings
Source: https://docs.wiacom.ai/client-reference/location-settings
Configure venue details, portal templates, registration methods, session rules, and data collection fields for each location.
**Location Settings** is the central configuration screen for each venue. All portal behaviour, branding, session rules, and data collection settings are managed here.
Select the venue to edit using the **Choose venue** dropdown at the top of the page.
## Location details
| Field | Notes |
| ------------------------ | ---------------------------------------------------------------------------- |
| Location name | Display name used in reports and portal pages |
| Location address | Physical address — shown on equipment reports |
| Default language | Language for all portal copy and outbound notifications |
| Template | Portal template default version (`V1`,`v2` · `v3` · `v4`) or your own design |
| Landing page (post-auth) | URL guests are redirected to after successful login |
Portal templates are not limited to built-in options. Your portal can be fully designed from scratch as a custom deployment — matching your brand identity, colour scheme, typography, and layout. Contact the Wiacom team to discuss a custom template for your organisation.
## Captive Portal Settings
Five tabs control the full portal guest experience.
***
### Tab 1 — Welcome
Controls what appears on the first screen before the guest starts the registration flow.
| Setting | Options |
| ---------------- | --------------------------------------------------- |
| Advertising type | **Image** · **Video** · **Text** |
| Media source | Upload via drag-and-drop or provide an external URL |
***
### Tab 2 — Portal
#### Registration methods
Each method can be independently toggled ON or OFF per location.
| Method | Type | Notes |
| --------------- | ------ | ------------------------------------------------------------------------- |
| Phone / OTP | Native | Phone number + SMS PIN verification |
| Email | Native | Email address + confirmation link |
| Facebook | OAuth | |
| Google | OAuth | |
| Apple | OAuth | Privacy relay may substitute a masked email |
| LinkedIn | OAuth | |
| Twitter / X | OAuth | |
| Instagram | OAuth | |
| Azure AD / O365 | OAuth | Corporate and enterprise SSO |
| Quick access | Native | Single-click access — no credentials required |
| Voucher | Native | Access code entry — see [Vouchers](/client-reference/data-plans/vouchers) |
#### Additional data fields
Optional fields displayed on the registration form. Each field has a **Status** toggle (shown / hidden) and a **Required** toggle (mandatory / optional).
| Field | Type |
| --------------- | ----------------------------------------------------- |
| Gender | Radio |
| Birthdate | Date |
| Name | Text |
| Register number | Text |
| Custom fields | Text / Radio / Date — defined per location on request |
Custom fields are configured by Wiacom on request. Contact [info@wiacom.ai](mailto:info@wiacom.ai) to define field name, type, and required status for your location.
**Accelerate collection** — when ON, returning users skip optional fields on subsequent visits. Only required fields are shown.
#### Sales page
An optional HTML or rich-text promotional page displayed between the registration form and the thank-you screen. Use for venue promotions, menus, event listings, or any content you want guests to see immediately after registering.
#### Additional info
Plain text or HTML block displayed alongside the registration form on the portal page itself.
***
### Tab 3 — Thank you
Configures the screen shown after the guest is successfully granted access.
Set a thank-you message and optionally a redirect button with label and URL (e.g. "Visit our website" → your venue homepage).
***
### Tab 4 — Welcome back
Controls the returning-user experience.
| Setting | Notes |
| ------------------------- | ------------------------------------------------------------------------------------- |
| Session validity | How long (in hours or days) the guest can browse before re-authentication is required |
| PIN validity (OTP method) | How long the SMS OTP code remains valid after being sent to the guest |
After the session validity window expires, the guest is shown the portal again on their next connection. Guests who registered via social login or email bypass the PIN step — they simply authorise the session again.
***
### Tab 5 — User data
Configure additional profile fields for business-specific data collection — for example, room number, staff ID, company name, or table number.
Each field has: name · type (text, radio, date) · status (shown / hidden) · required flag.
Data collected here is stored against the guest's identity record and is available in reports and exports.
# Ops Intelligence
Source: https://docs.wiacom.ai/client-reference/ops-intelligence
AI-assisted operational intelligence for monitoring network health, diagnosing issues, and auditing access events — currently in closed beta.
**Ops Intelligence is currently in closed beta.** This feature is not yet available on standard accounts. The documentation below describes the intended functionality. Contact [info@wiacom.ai](mailto:info@wiacom.ai) if you are interested in early access.
Ops Intelligence is an AI-assisted operational layer that surfaces network health signals, diagnoses connectivity issues, and provides an auditable log of AI-generated recommendations — all from a single interface across your locations.
## Planned sub-sections
### Dashboard
Real-time operational health view across all locations — AP status summary, open incident count, anomaly signals, and alert indicators.
### Incidents
Log of detected operational events: AP offline, authentication failure spikes, abnormal traffic patterns. Each incident shows severity level, affected location and AP, detection timestamp, and resolution status.
### Troubleshoot User
AI-generated diagnosis for a specific guest. Enter an identity reference to retrieve recent session history and recommended remediation steps.
### AI Audit Log
A full chronological record of all decisions and recommendations generated by the Ops Intelligence engine. Used for compliance review and to verify AI-suggested changes before or after they are applied.
### Settings
Configure alert thresholds, notification destinations, and integration settings for the Ops Intelligence engine.
***
*This page will be updated when Ops Intelligence reaches general availability.*
# Access Tracker
Source: https://docs.wiacom.ai/client-reference/settings/access-tracker
Search and investigate individual device access history for troubleshooting purposes.
**Access Tracker** is a diagnostic tool for investigating device access history. It is intended for use by designated IT personnel within your organisation for troubleshooting connectivity issues and handling data subject requests.
Access to this section is restricted to authorised personnel only. It should not be used for general account management or marketing purposes.
## Searching
Search by any of the following:
* Phone number
* Name (partial matches supported)
Click **Search**. Results show all records matching the query.
## What the results show
For each matched record:
| Field | Description |
| ------------------- | ------------------------------------------------ |
| Location | Location where the registration occurred |
| Registration method | Login method used (Phone, Email, Facebook, etc.) |
| Registration date | When the guest first registered |
| Last login | Timestamp of most recent session |
| Visit count | Total number of return visits |
| Status | Active / Suspended / Revoked |
| Session history | Recent sessions with timestamps and AP details |
In compliance with GDPR, no personally identifiable information is displayed in full. The platform does not show names, email addresses, or complete phone numbers at any point.
## Use cases
* **Connectivity troubleshooting** — investigate why a specific device is not connecting or is being rejected.
* **Access investigation** — verify whether a specific registration has active credentials and when they were last used.
* **Data subject requests** — locate records associated with a specific individual to support GDPR access or deletion requests. This should be handled only by your designated data protection contact in accordance with your organisation's internal procedures.
# Email Registration Settings
Source: https://docs.wiacom.ai/client-reference/settings/email-registration-settings
Per-location configuration for email-based authentication — session timeouts, attempt limits, and confirmation URL management.
**Email Registration Settings** controls the behaviour of email-based WiFi authentication for each of your locations. Settings are applied per location and can be viewed across all locations at once or filtered to a single venue using the location selector at the top of the page.
## Location selector
Use the dropdown to filter the table to a specific location, then click **Filter**. Leave the selector on the default option to view all locations simultaneously.
## Settings table
Each row represents one location. The following columns are shown:
| Column | Description |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Location** | Venue name |
| **Session timeout** | How long (in minutes) an email-authenticated session remains valid before the guest must re-authenticate |
| **Email attempts** | Maximum number of email authentication attempts allowed before the guest is locked out |
| **Timeout interval** | Waiting period (in seconds) enforced between failed attempts |
| **Confirmation URL** | The URL embedded in the confirmation email sent to the guest. Defaults to the location landing page if no specific confirmation URL is set |
| **Link** | A test link to verify the confirmation URL is reachable and resolves correctly |
| **Actions** | Edit button — opens the configuration form for that location |
| **Forget cache** | Clears the cached session and configuration data for the location immediately |
## Editing a location
Click **Edit** on the location row to update its email authentication settings. The edit button is disabled on locations where login options are locked — contact your Wiacom account administrator if you need to make changes to a locked location.
## Forget cache
The **Clear all Cache** button on each row flushes the cached configuration for that location. Use this after making changes if updated settings are not immediately reflected for connecting guests.
Sender configuration, email template content, and marketing consent text are managed at the account level by your Wiacom administrator — they are not configurable from this screen.
# MAC Users
Source: https://docs.wiacom.ai/client-reference/settings/mac-users
Search, create, edit, and troubleshoot MAC-authenticated device records.
**MAC Users** manages devices that are granted WiFi access by MAC address — without going through the captive portal registration flow. The section has two pages: **Search** (list and manage existing records) and **Add New** (create a new record).
## Search
Find existing device records using one of five search modes. Select the search type from the **Search By** dropdown, fill in the corresponding field, and click **Search**.
| Search by | Input |
| --------- | ---------------------------------------- |
| **MAC** | Device hardware address |
| **Email** | Email address associated with the record |
| **Name** | Label assigned to the device |
| **Room** | Room identifier |
| **Type** | Select from: Guest · Staff · Device |
An optional **Location** filter and **Interval** (date range) filter can be combined with any search mode to narrow results further.
## Results table
Each row represents one device record. Rows with a passed expiry date are highlighted in yellow.
| Column | Description |
| ---------- | --------------------------------------------------------- |
| MAC | Device hardware address |
| Name | Descriptive label |
| Type | Guest · Staff · Device |
| Vendor | WiFi vendor associated with this record — shown as a logo |
| Email | Email address if provided |
| Room | Room identifier if provided |
| Location | Venue this record belongs to |
| Created at | Record creation timestamp |
| Expire on | Access expiry datetime, or blank if no expiry is set |
| Updated on | Last modification timestamp |
| Actions | **Edit** · **Troubleshoot** · **Delete** |
## Edit
Click **Edit** on any row to open the edit modal. The following fields can be updated:
* Name
* Type (Guest / Staff / Device)
* Room
* Email
* Expiration date and time
* Location
The device MAC address is displayed in the modal header for reference and cannot be changed. Click **Save Changes** to apply.
## Troubleshoot
Click **Troubleshoot** on any row to open the trace details modal for that device. The modal loads the following diagnostic sections:
**Credential status** — whether the device has a valid access record and what state it is in.
**Online status** — whether the device currently has an active session.
**Traffic statistics** — session duration and data volume over time, rendered as a chart. Two series are shown: session time and total traffic (download + upload).
**Authentication logs** — a timeline of access attempts for this device, rendered as a chart. Two series are shown: accepted and rejected attempts.
**Interval selector** — by default the modal loads recent data. Use the **Start time** and **End time** fields and click **Update Interval** to analyse a specific historical window.
**Export to PDF** — the full modal content (excluding the interval selector controls) can be exported as a PDF file. The filename includes the device MAC address.
## Add New
Navigate to **Settings → Create MAC User** to create a new record. Fill in the following fields:
| Field | Required | Description |
| ----------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| MAC address | Yes | Hardware MAC address of the device |
| Name | Yes | Descriptive label — e.g. "Lobby kiosk", "POS terminal 3", "Room 204 tablet" |
| Location | Yes | Venue where this device will connect |
| Type | Yes | **Guest** · **Staff** · **Device** |
| Email | No | Optional email address for reference |
| Room | No | Room number or identifier |
| Expire on | No | If set, access is automatically revoked after this datetime |
| WiFi vendor | Yes | The hardware vendor profile for this location. Auto-populated based on the selected location — change only if the device connects via a different vendor than the location default |
The WiFi vendor selection determines how the device's access credentials are generated internally. It defaults to the primary vendor configured for the selected location. Only change it if you are provisioning a device on a secondary or different vendor at that location.
Click **Add User** to create the record. The device will be granted access on its next connection attempt without going through the captive portal.
MAC address authentication can be bypassed by devices that spoof hardware addresses. Use MAC Users only for trusted, managed devices — kiosks, POS terminals, IoT sensors, digital signage, and similar equipment. It is not suitable as the sole access control mechanism in security-sensitive environments.
# Router Settings
Source: https://docs.wiacom.ai/client-reference/settings/router-settings
View and manage SSIDs, passwords, and safe browsing settings for all APs registered to the account.
**Router Settings** shows all APs registered to the account across all locations, with their current SSID configuration.
## Router table
| Column | Description |
| ------------- | ---------------------------------------------- |
| Location | Venue this AP belongs to |
| Router tag | Friendly name assigned in inventory |
| MAC | Hardware MAC address |
| Public SSID | Guest-facing network name |
| Private SSID | Staff or management network name |
| Model | Hardware model — auto-detected where supported |
| Status | Online / Offline indicator |
| Password | Masked passphrase — click to reveal or edit |
| Safe browsing | Content filtering toggle for the guest network |
| Actions | Edit button |
## Editing a router
Click the edit icon (pencil) on any row to open the router detail view. From here you can update the router tag, SSID names, passphrase, and safe browsing setting.
For API-connected controllers (such as Meraki or UniFi), SSID name and password changes made here are pushed to the controller automatically on save. For manually onboarded hardware, changes must be applied directly on the device — Wiacom has no API connection to push them.
## Safe browsing
When the **Safe browsing** toggle is ON, content filtering is applied to the guest network on supported hardware. This blocks access to categories of websites considered inappropriate for public venues. The filter list is managed by Wiacom. Contact [info@wiacom.ai](mailto:info@wiacom.ai) to review or customise the filter categories for your account.
# Advanced Campaigns Stats
Source: https://docs.wiacom.ai/client-reference/stats/advanced-campaigns-stats
Detailed SMS and email delivery report for all advanced campaigns.
**Advanced Campaigns Stats** is the detailed delivery log for both SMS and email campaigns combined. Use this to monitor delivery performance, identify blocklist issues, and track email engagement.
## Table columns
| Column | Description |
| --------------- | --------------------------------------- |
| Status SMS | Delivery status for the SMS component |
| Status Email | Delivery status for the email component |
| Campaign | Campaign name |
| Date | Scheduled send datetime |
| SMS | Number of SMS messages in this campaign |
| Email | Number of emails in this campaign |
| Sender | Sender name used for SMS |
| Contacts SMS | Number of contacts targeted for SMS |
| Blacklist SMS | Contacts excluded due to blocklist |
| Contacts Email | Number of contacts targeted for email |
| Openings Email | Number of email opens |
| Clicks Email | Number of link clicks within the email |
| Blacklist Email | Contacts excluded from email delivery |
| Options | Actions available for this campaign |
## Campaign statuses
| Status | Meaning |
| -------------- | ------------------------------------------- |
| **Processed** | Campaign has been fully sent |
| **Programmed** | Campaign is scheduled and has not yet fired |
| **Cancelled** | Campaign was cancelled before sending |
## Cancelling a programmed campaign
For campaigns with a **Programmed** status that have not yet fired, a **Cancel E-MAIL** button is available in the Options column. SMS campaigns can be cancelled from the [Campaigns report](/client-reference/stats/campaigns-report).
# Campaigns Report
Source: https://docs.wiacom.ai/client-reference/stats/campaigns-report
Table of all sent and scheduled SMS campaigns with delivery counts and management options.
The **Campaigns** report shows every SMS campaign on the account — sent, scheduled, and cancelled.
## Table columns
| Column | Description |
| --------------- | ------------------------------------------------------------- |
| Status | Campaign state — see below |
| Campaign name | Internal name set when the campaign was created |
| Date | Scheduled or actual send datetime |
| Location | Location(s) targeted |
| Type | Contact segment used (e.g. All contacts, Active last 30 days) |
| Sender | SMS sender name |
| SMS | Total SMS messages created |
| Contacts | Number of contacts targeted |
| Blocked numbers | Contacts excluded due to blocklist |
| Sent | Messages confirmed sent to the operator |
| Options | Edit or cancel actions |
## Status values
| Status | Meaning |
| --------------------- | ------------------------------------------------- |
| `Sent` (green) | Campaign has been fully delivered to the operator |
| `Programmed` (blue) | Campaign is scheduled and has not yet fired |
| `0 Contacts` (yellow) | Campaign ran but matched no eligible contacts |
## Managing scheduled campaigns
Campaigns with a **Programmed** status can be edited or cancelled from the Options column, as long as the send time has not yet passed.
* **Edit** — opens the Advanced Campaign wizard pre-filled with the existing configuration. All fields can be modified.
* **Cancel** — permanently cancels the campaign. This action cannot be undone.
A campaign can only be cancelled while its status is **Programmed**. Once the platform begins processing a send, cancellation is no longer possible — the campaign will complete delivery to all matched contacts. Always verify your audience segment and message content before scheduling.
Once a campaign status changes to `Sent`, it cannot be recalled or deleted.
# Stats
Source: https://docs.wiacom.ai/client-reference/stats/index
The Stats submenu — live user views, analytics dashboards, campaign reports, and the message sentbox.
The **Stats** submenu contains eight reporting and analytics items, split into two groups:
**Live user views** — real-time snapshots of who is connected right now.
| Item | What it shows |
| ------------ | ------------------------------------------------ |
| Online Users | Devices currently connected at the network layer |
| User Reports | Users with an active Wiacom session |
**Analytical reports** — historical data, aggregates, and export tools.
| Item | What it shows |
| ------------------------ | ------------------------------------------------------------------------ |
| Social / Demo Reports | Anonymised demographic breakdown of your audience |
| Traffic Analytics | Full analytics dashboard — connections, funnel, AP distribution, traffic |
| Advanced Campaigns Stats | Per-campaign SMS and email delivery detail |
| Campaigns | Table of all sent and scheduled SMS campaigns |
| Sentbox | Per-message SMS delivery log |
Select a page from the left navigation for full details on each report.
# Online Users
Source: https://docs.wiacom.ai/client-reference/stats/online-users
Real-time list of devices currently connected to your WiFi.
**Online Users** shows every device connected at the network layer to any AP in your account, right now. The list refreshes automatically.
In compliance with GDPR, this report only includes users who have given marketing consent. No personally identifiable information is displayed — the platform does not show names, email addresses, or full phone numbers at any point.
## Filters
Narrow the view using any combination of:
| Filter | Options |
| ------------------------- | ------------------------------------------------------------------------------------ |
| Location | Single venue or all locations |
| Min / Max connection hour | Show only connections that occurred within a specific time window (e.g. 08:00–22:00) |
| Customer visits range | Minimum and maximum return visit count — use to surface loyal regulars |
| Age range | Guest age band (requires age collection enabled on the portal) |
| Gender | All / Male / Female |
| Login method | Phone, Facebook, Google, Apple, LinkedIn, Twitter/X, Instagram, Azure AD |
Click **Filter** to apply. The list updates immediately.
## User cards
Each entry in the list shows:
* Location and AP the device is connected to
* Last login timestamp
* Total return visit count
* Return visit count in the last 30 days
* Login method icon
* Registration type indicator
## Sending an SMS to connected users
Check **Send SMS message to selected visitors** at the top right of the page. Select one or more users from the list, compose your message, and send.
SMS sends initiated from this screen are recorded and visible in the **Sentbox** and **Campaign Stats** sections of the Stats menu, alongside all other outbound messages.
SMS can only be sent to users who have provided a verified phone number and given marketing consent. Users without consent are not shown in this list.
Use this for in-the-moment messaging — for example, notifying currently connected guests about a limited-time offer or an event starting now.
# Sentbox
Source: https://docs.wiacom.ai/client-reference/stats/sentbox
Per-message SMS delivery log with individual delivery status for every message sent.
The **Sentbox** is the per-message delivery log for all SMS activity on the account. Where the Campaigns report shows campaign-level totals, the Sentbox shows the delivery status of each individual message.
## Table columns
| Column | Description |
| -------- | ---------------------------------------- |
| Campaign | Campaign name this message belongs to |
| Location | Venue associated with the send |
| Sender | SMS sender name |
| SMS | Message text (truncated) |
| Date | Send datetime |
| Status | Per-message delivery outcome — see below |
## Delivery statuses
| Status | Meaning |
| -------------------- | ---------------------------------------------------------------------------------- |
| **Delivered** | The SMS arrived on the recipient's device |
| **Undelivered** | The device was off, out of coverage, or the number was invalid at delivery time |
| **Sent to operator** | The message reached the mobile carrier but has not yet been confirmed as delivered |
| **Waiting** | The message is queued and will be sent |
Delivery confirmation depends on mobile network operator reporting. Some operators do not return delivery receipts, in which case a message may remain at **Sent to operator** status permanently even if it was received by the guest.
# Social / Demo Reports
Source: https://docs.wiacom.ai/client-reference/stats/social-reports
Anonymised demographic breakdown of your registered WiFi audience.
**Social / Demo Reports** shows aggregate audience profiling data for your registered guests. All data is fully anonymised — no individual user records are exposed.
## Charts
Four donut charts update live when you change the location filter:
| Chart | What it shows |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Gender** | Male / Female split across all registered users |
| **Age bands** | Distribution across: 14–17 · 18–24 · 25–34 · 35–44 · 45–54 · 55–64 · 65+ |
| **Device type** | Mobile vs Desktop / laptop |
| **Authentication method** | Breakdown by registration source — Phone, Email, Facebook, Google, Apple, LinkedIn, Twitter/X, Instagram, Azure AD, Quick access, Voucher |
## Filter
Select a single location or view aggregated data across all locations using the location dropdown at the top of the page. All four charts update simultaneously.
Age and gender data is only available for guests who provided this information during registration. If optional data collection fields are not enabled on your portal, these charts will show limited data.
# Traffic Analytics
Source: https://docs.wiacom.ai/client-reference/stats/traffic-analytics
The main analytics dashboard — connections, portal funnel, AP distribution, traffic accounting, and PDF exports.
**Traffic Analytics** is the primary analytics view. It loads asynchronously — each section fetches data independently so charts appear progressively as they resolve. Individual section failures degrade gracefully with inline error panels rather than breaking the whole page.
Traffic Analytics availability depends on your account plan. Contact your Wiacom account manager if this section is not visible or shows a limited view.
## Date range
Select the reporting period using the preset shortcuts at the top of the page:
**Today · Last 7 days · Last 30 days · Last 90 days · Custom**
For a custom range, use the calendar picker to select start and end dates. All sections update simultaneously on filter change.
## Sections
### Connections over time
Daily unique device count across the selected period, with new vs returning visitor split. Includes a peak-hour bar chart showing which hour of day receives the most connections.
### Peak stats
* **Busiest day** — the calendar date with the highest unique device count in the period
* **Peak concurrent users** — the highest number of simultaneously active sessions recorded
### Registration breakdown
Six source cards showing how your audience registered:
| Card | Source |
| ------------ | ------------------------------------------------ |
| Phone / OTP | Registered via phone number and SMS verification |
| Email | Registered via email address |
| Social | Registered via a social or identity provider |
| Quick access | Single-click access without credentials |
| Voucher | Authenticated via access code |
| Other | Additional registration sources |
### Portal funnel
Drop-off analysis between each screen of the captive portal flow:
```
Welcome → Login → Data Collection → Thank You
```
Shows the count of unique devices at each stage and the drop-off percentage between stages. Use this to identify where guests are abandoning the registration flow.
### AP / Zone distribution
* Per-AP connection counts for all APs in the selected location(s)
* Per-zone treemap view (where zones are configured)
* Map view with AP locations (where coordinates are configured on the AP records)
### Dwell time
Per-zone minimum, average, and maximum session duration.
### Traffic accounting
Download and upload data volume aggregated by day or by AP.
### Email analytics
Funnel for email-registration and Guest Connect flows:
**Sent → Opened → Confirmed → Bounced**
Shows counts and conversion rates at each stage.
### Device & platform
Browser, operating system, and device brand distribution across all sessions in the period.
## Multi-location mode
When more than one location is selected, each section shows per-location donut chart breakdowns alongside the aggregate view. Location grouping is applied automatically.
## PDF export
Click the **Export** button at the top right to generate a downloadable PDF report. Three variants are available:
| Variant | Audience | Contents |
| ------------- | ---------------- | -------------------------------------------------------------------- |
| **Marketing** | Marketing team | Portal funnel, registration breakdown, email analytics, demographics |
| **IT** | Network / IT ops | AP distribution, traffic accounting, session stats |
| **Full** | Management | All sections combined |
PDF exports always reflect live data at the moment of generation.
# User Reports
Source: https://docs.wiacom.ai/client-reference/stats/user-reports
Users with an active Wiacom session — historical and live, with loyalty filtering.
**User Reports** shows guests who have a live Wiacom session — meaning they have completed registration and been granted internet access. Unlike Online Users, this report supports a date range filter for historical session queries.
## Filters
| Filter | Options |
| ------------------------- | ------------------------------------------------------------------------ |
| Connection interval | Date range — query sessions in a historical period |
| Location | Single venue or all locations |
| Min / Max connection hour | Session time window within the day |
| Customer visits range | Min and max return visit count |
| Age range | Guest age band |
| Gender | All / Male / Female |
| Login method | Phone, Facebook, Google, Apple, LinkedIn, Twitter/X, Instagram, Azure AD |
## Loyalty filtering
The **Customer visits (returns)** filter is the primary loyalty tool. Examples:
* Set minimum visits to `5` to find guests who have returned at least five times — ideal for a loyalty reward campaign.
* Set maximum visits to `1` to find first-time visitors only — useful for a welcome follow-up.
* Combine with a date range to find guests who visited frequently in a past period but have not returned recently.
## User cards
Each card shows the same fields as Online Users — partial name, contact, location, last login, total returns, returns in last 30 days, and login method — but also reflects the historical session data matched by the connection interval filter.
# Platform Overview
Source: https://docs.wiacom.ai/getting-started/platform-overview
Access features, onboarding channels, equipment integration modes, and platform services.
## Platform Structure
Wiacom has two administration sides:
| Side | Who uses it | What it manages |
| ------------------ | ----------------------------- | ------------------------------------------------------------------------- |
| **MSP / Admin** | Wiacom partners and resellers | Customer accounts, inventory, controller onboarding, compliance settings |
| **Client account** | Venue operators | Portal visuals, registration forms, campaigns, analytics, troubleshooting |
The inventory hierarchy is: **Access Points → Zones → Location → Customer account**. Each location belongs to exactly one business name (required for data protection compliance).
Wiacom separates infrastructure administration from venue-level operations. The MSP/Admin side controls customer setup, inventory, vendor integration, compliance configuration, and platform provisioning. The Client Account side gives venue operators control over their own portal experience, user onboarding, campaigns, reports, and operational troubleshooting. This separation allows partners to manage infrastructure centrally while customers manage their own guest-facing WiFi experience.
Wiacom also includes a dedicated **User Portal (WUP)** for registered WiFi users. This portal allows end users to access and manage their personal data, privacy preferences, consent status, and related GDPR requests through a self-service interface.
While the **MSP/Admin** and **Client account** areas are used by operators, partners, and venue teams, the **User Portal** is designed for the registered user. It provides transparency and control over personal data, supports GDPR compliance, and reduces manual workload for legal and support teams.
## Access Features
Access features define how a validated user is granted WiFi connectivity. Each access feature maps to specific WiFi technology supported by one or more vendors.
| Feature | Technology | Controller API required |
| --------------------- | ---------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Portal** | Captive portal + RADIUS per-user credential authentication | Optional (API or manual config) |
| **WiFi Pass** | iPSK / MPSK / DPSK / other, with or without RADIUS | Required if no RADIUS or no [Wiacom Agent](/integrations/wiacom-agent) |
| **Key Access** | Shared WPA2 PSK | Optional |
| **Passpoint Connect** | Hotspot 2.0 / Passpoint + RADIUS | Optional |
| **Horizon** | Personal SSID / WiFi teleport + lifecycle management | Required if no [Wiacom Agent](/integrations/wiacom-agent) |
## Onboarding Channels
Onboarding channels are how users register, are identified, and trigger an access flow. A user can be onboarded through one channel and then access via any configured access feature.
| Channel | Description | Status |
| ------------------------- | ---------------------------------------------------------------- | ----------- |
| **Guest Connect** | Self-service registration by URL or QR code | ✅ Available |
| **Captive Portal** | Inline onboarding during Portal access flow | ✅ Available |
| **API** | Programmatic identity creation from external systems | Available |
| **Wiacom Horizon** | Identity-driven SSID provisioning | Available |
| **SDK** | Onboarding inside third-party mobile apps | Available |
| **PMS / CRM integration** | Hotel PMS (OPERA Cloud / OHIP), CRM, loyalty, enterprise systems | Available |
| **Student Connect** | Student onboarding with institutional identity | Coming soon |
| **Staff Connect** | Staff and contractor onboarding | Coming soon |
### Sign-up and Identity Methods
Regardless of the onboarding channel, Wiacom supports multiple identity verification and registration methods:
* Email sign-up with confirmation
* Phone registration with PIN / OTP verification
* Social login through Identity Providers (IdPs), including but not limited to Google, Apple, Facebook, LinkedIn, X / Twitter, Microsoft, and other supported providers
* Enterprise OAuth / SSO integrations, including Microsoft Entra ID / Azure AD, Office 365, and other compatible identity platforms
* [Voucher-based](client-reference/data-plans/vouchers) registration, Internet Access Plans
* API-created identities
* Pre-registered identities, created by an administrator or imported in bulk
* Custom business integrations
## Post-Validation Access Flow
After a user is successfully validated through any onboarding channel, Wiacom applies the access workflow configured for that location:
* Captive portal RADIUS authorisation (per-user auto-generated credentials)
* RADIUS Access-Accept
* Unique PSK (iPSK / MPSK) provisioning
* Passpoint profile delivery
* Personal SSID provisioning (Horizon)
* Expiry, quota, bandwidth, and session policy enforcement
For public venues and guest access, users also receive a link to a **self-service privacy page** where they can manage personal data, consent records, and exercise their data protection rights.
## Equipment Onboarding
WiFi equipment is integrated with Wiacom in two modes:
### Legacy Mode (Manual)
For any vendor — no API integration required.
1. **Single device:** Go to **Inventory → Routers → Add New Router**, select vendor, fill details, assign a location.
2. **Bulk import:** Go to **Inventory → Routers → Unallocated Routers → Import from Excel**. Download the template, fill it in, select vendor and location, upload.
Manually configure the device with the RADIUS server and portal URL provided by Wiacom for your region.
### API Mode (Controller Integration)
For vendors with API support. Wiacom connects to the vendor cloud, discovers networks and SSIDs, assigns roles, and pushes configuration automatically.
1. Go to **Inventory → Controllers → Add Controller**.
2. Select vendor, enter API credentials.
3. Map networks to Wiacom locations.
4. Assign SSID roles (Portal / WiFi Pass / Key Access).
RADIUS server addresses and portal redirect URLs are region-specific. The correct values for your deployment are shown in the Wiacom admin panel or provided by the Wiacom team.
## Deployment Options
Wiacom supports three deployment models to accommodate different commercial, branding, and infrastructure requirements.
### Cloud-Hosted (Standard)
The default model. Wiacom operates the platform on its own cloud infrastructure. Customers access the platform through a dedicated subdomain under the Wiacom root domains.
### White-Label
The platform can be deployed under a partner or customer brand. In white-label mode:
* The platform is served from a **customer-owned or partner-owned domain** (e.g. `wifi.yourbrand.com`), configured via DNS CNAME to the Wiacom infrastructure
* All portal pages, registration flows, dashboards, and email communications can be fully rebranded — logo, colour scheme, domain, sender identity
* No Wiacom branding is visible to end users or venue operators unless specifically agreed
* SSL/TLS certificates are provisioned for the custom domain as part of the setup
White-label deployments are typically used by MSPs, resellers, and enterprise operators who deliver the service under their own brand.
### Customer-Hosted (On-Premise / Private Cloud)
The Wiacom platform can be deployed on customer-owned or customer-managed infrastructure. This option is available for operators with specific data residency, network isolation, or compliance requirements that preclude use of shared cloud infrastructure.
Customer-hosted deployments require server infrastructure meeting Wiacom's minimum specifications, and the deployment and ongoing maintenance are scoped and agreed with the Wiacom team.
White-label and customer-hosted deployments are not self-service. Both require scoping and configuration by the Wiacom team. Contact Wiacom to discuss requirements and commercial arrangements.
## Platform Services
| Service | Description | More |
| -------------------------- | -------------------------------------------------------------------------------- | ------------------------------------- |
| **Identity & Consent** | GDPR-compliant registration, consent records, configurable data retention | |
| **Privacy page** | Guest self-service for data access, correction, and erasure requests | |
| **Multi-location / MSP** | Centralised admin for unlimited locations; multi-tenant MSP support | |
| **Analytics & Reporting** | Visit frequency, dwell time, new vs. returning, registration funnel, data export | |
| **Audience Activation** | Segment and export guest lists for CRM, email, or CDP integration | |
| **Messaging Services** | Platform-provided transactional email, SMS, RCS, and WhatsApp | [Details](/integrations/messaging) |
| **CRM & CDP Integrations** | Push data to external platforms through approved partner channels | [Details](/integrations/crm-cdp) |
| **API & Webhooks** | REST API and webhook events for custom integration | [Details](/integrations/api-webhooks) |
| **PMS Integration** | OPERA Cloud / OHIP and other PMS connectors | |
| **AdFlow / AdService** | Inject promotional content into the portal onboarding journey | |
| **Billing** | Prepaid (top-up) and postpaid billing; payment gateway integration available | |
| **Data Models** | Configurable retention interval; optional push to customer systems | [Details](/integrations/data-models) |
| **Deployment Options** | Cloud-hosted, white-label, or customer-hosted | |
## Data & Security
* All data processed and stored in compliance with GDPR
* Guest PII is never transmitted to WiFi vendors — only anonymised credentials reach controllers
* All platform communication uses HTTPS / TLS 1.2+
* Credentials encrypted in transit and at rest
Wiacom is hosted primarily on Microsoft Azure and Google Cloud, with Amazon Web Services used where required for selected components or customer-specific deployments. These providers maintain independently audited security, privacy, and compliance programs, including ISO/IEC 27001, ISO/IEC 27017, ISO/IEC 27018, SOC 1, SOC 2, SOC 3, CSA STAR, PCI DSS, GDPR support programs, and other regional or sector-specific frameworks where applicable.
# Quick Start
Source: https://docs.wiacom.ai/getting-started/quick-start
Get started with Wiacom
Wiacom is set up in collaboration with the Wiacom team or an authorized Wiacom partner. The fastest way to get your first location live is to request a demo — the team will walk you through the platform, understand your infrastructure, and get everything configured together.
Book a session with the Wiacom team to get your first location set up
## What to Expect
During your onboarding session the Wiacom team will:
* Set up your account and create your first location
* Connect your WiFi infrastructure (API, Local Config or Wiacom Agent).
* Configure the onboarding channel and access features for your venue
* Customize your portal or Guest Connect page with your branding
* Walk you through the admin panel and reporting
## Before the Session
It helps to have the following ready:
| Item | Notes |
| ---------------------------- | ----------------------------------------------- |
| WiFi vendor and model | e.g. Cisco Meraki, Ruckus SmartZone, MikroTik |
| Controller access | API key (if API-connected) or admin credentials |
| Venue details | Name, address, timezone |
| Brand assets | Logo, brand colors |
| Preferred onboarding channel | Guest Connect, portal, or API |
## Self-Service Reference
While the guided setup is handled with the Wiacom team, this documentation covers everything you need to understand and manage the platform afterwards:
Access features, onboarding channels, and integration modes
Portal, WiFi Pass, Key Access, Passpoint Connect, Horizon
Setup guides for all supported hardware
Platform concepts and architecture
# External APIs & Webhooks
Source: https://docs.wiacom.ai/integrations/api-webhooks
Connect external systems, automate workflows, and consume Wiacom data programmatically via REST API and webhook events.
This page is being expanded. API documentation and webhook event reference will be published here. Contact the Wiacom team for current API access and integration scoping.
Wiacom exposes a REST API for programmatic access to registration data, credential management, session control, and reporting. API access requires strong authentication and can be restricted by source IP at the account level.
Webhook events are available for key platform actions — including new registrations, credential provisioning, session events, and expiry — enabling real-time integration with external workflows and automation platforms.
Custom SDK integration is available for mobile applications and third-party middleware requiring deeper connectivity into the Wiacom identity and access layer.
# CRM & CDP Integrations
Source: https://docs.wiacom.ai/integrations/crm-cdp
Push guest data into your CRM, CDP, or marketing platform — through Wiacom-managed connectors or your own integration.
Wiacom can push guest registration and engagement data into external CRM, CDP, and marketing automation platforms. Integrations are provisioned securely on the backend.
Supported integration patterns include scheduled exports, real-time push on registration or event trigger, and audience segment synchronisation for remarketing activation.
Data exposed through these integrations is subject to the consent captured at registration. Only data where valid consent exists is transmitted to external platforms.
## Supported Platforms
Wiacom has integrations in place for a large number of major and regional CRM and CDP platforms. The list of supported systems is extensive and continues to grow — if you are using an established platform, there is a good chance it is already supported.
Contact the Wiacom team with your platform of choice to confirm availability, data mapping requirements, and any configuration steps needed on your side.
## Integration Options
Two approaches are available:
**Wiacom-managed connectors** — for platforms where a Wiacom integration is already in place. Setup is handled on the backend by the Wiacom team with minimal configuration required from the customer.
**Customer API integration** — for platforms not yet covered by a Wiacom connector. If your CRM or CDP exposes a standard inbound API, Wiacom can be configured to push data directly to it. The customer is responsible for providing API credentials, defining the data schema, and managing their platform's inbound configuration.
For the full list of supported CRM and CDP platforms, or to discuss integration requirements for a platform not yet listed, contact the Wiacom team.
# Data Models
Source: https://docs.wiacom.ai/integrations/data-models
Two supported data-flow architectures: Wiacom as a Data Vault with configurable retention, or Wiacom as privacy-minimised middleware.
Wiacom supports two distinct data-flow models. The appropriate model depends on the customer's data governance requirements, existing infrastructure, retention policy, lawful basis, and data-minimisation requirements.
Both models are designed to support GDPR-compliant deployments when implemented with the appropriate contractual, technical, organisational, retention, consent, and security controls.
They differ in where personal data is held, which system acts as the primary system of record, and what responsibilities the customer assumes.
Wiacom is hosted primarily on Microsoft Azure and Google Cloud, with Amazon Web Services used where required for selected components or customer-specific deployments. These providers maintain independently audited security, privacy, and compliance programs, including ISO/IEC 27001, ISO/IEC 27017, ISO/IEC 27018, SOC 1, SOC 2, SOC 3, CSA STAR, PCI DSS, GDPR support programs, and other regional or sector-specific frameworks where applicable.
## Model 1 — Wiacom as Data Platform / Data Vault
This is the **default operating model**.
In this model, Wiacom acts as a secure **Data Platform** and **Data Vault** for registration, consent, session, engagement, and WiFi usage data. Data is stored for a configured retention interval and used to provide analytics, reporting, audience activation, troubleshooting, and engagement capabilities.
Data retention duration is configurable per deployment. After the retention interval expires, data is purged in accordance with the applicable data protection policy.
Model 1 can also be configured so that selected personal data is pushed to customer systems — such as a CDP, CRM, PMS, or another approved platform — while Wiacom continues to operate the access control, onboarding, analytics, and reporting layers.
Customer access to data held in Wiacom is provided through secure, controlled channels:
| Access Method | Notes |
| ----------------- | ------------------------------------------------------------------------------------------------ |
| HTTPS REST API | Strong authentication required; source IP restrictions available |
| Scheduled exports | Periodic data exports to a customer-designated destination |
| Push to CDP / CRM | Real-time or automated push into approved external platforms on a configured schedule or trigger |
### Data Available
The following data may be exposed, subject to the configured consent, legal basis, and deployment rules:
| Data Type | Notes |
| -------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| Email address, phone number, and other personal or profile-related details | Only where collected lawfully for access, service operation, or marketing, depending on the configured flow |
| Confirmed and non-confirmed registrations | Where a valid email was provided at sign-up |
| Sign-up date and return visit history | Visit frequency and loyalty indicators |
| Dwell time | Session duration per visit |
| Portal funnel stage | Stage reached in the registration journey |
| Email delivery and engagement | Open, click, confirmation, and delivery tracking |
| Traffic and behaviour analytics | Selected session and usage metrics |
| Custom metrics | Available where specifically configured for a deployment |
The platform does not expose raw guest names or email addresses in standard analytics views. Reports and dashboards are scoped according to the configured consent and data-processing rules for the deployment. Full PII export is available only through authenticated API or scheduled export, where permitted by the applicable consent and legal basis.
### Who Holds the Data
In this model, **Wiacom acts as a data processor** on behalf of the customer. A Data Processing Agreement (DPA) governs this relationship.
The customer remains the data controller and retains rights over guest data, including export and deletion requests, subject to the agreed processing terms and applicable law.
Model 1 is designed for fast deployment and is typically the most suitable option for small and medium-sized customers that do not want to operate their own data platform, CRM, consent storage, or transactional messaging infrastructure.
It provides a ready-to-use operating model with standard Wiacom terms, consent flows, data-retention controls, and portal documentation. Default terms and conditions templates are available and have been reviewed by reputable professional legal advisers, although customers remain responsible for validating their final deployment, notices, and lawful basis according to their own jurisdiction and internal policies.
This model is available for deployments in multiple markets and is intended to provide broad operational coverage with minimal customer-side implementation effort.
***
## Model 2 — Wiacom as Middleware / Privacy-Minimised
This is a **custom implementation** available for customers with stricter data minimisation, data residency, or internal governance requirements.
In this model, Wiacom acts primarily as an integration and enforcement layer. Personal data is pushed directly to the customer's own CDP, CRM, PMS, or another approved external system at the point of collection.
Wiacom retains only a unique pseudonymous user identifier and the technical data required for WiFi authentication, session control, reporting, SLA monitoring, security, and troubleshooting.
Pseudonymous identifiers may still be considered personal data where they can be linked back to an individual by the customer or another authorised system.
### What Wiacom Retains
| Data Retained by Wiacom | Purpose |
| ------------------------------------ | ---------------------------------------------------------------------- |
| Unique pseudonymous user identifier | Cross-session recognition and credential linkage |
| Technical authentication credentials | WiFi access enforcement, including RADIUS, iPSK, or similar mechanisms |
| Session and connection metadata | Reporting, troubleshooting, SLA monitoring, and security analysis |
### Customer Responsibilities
| Requirement | Detail |
| ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| System of record | The customer's platform becomes the primary store for personal data |
| External API availability | Customer APIs must be accessible from Wiacom infrastructure for real-time data push |
| Transactional messaging | The customer must provide their own email and SMS delivery services, including API credentials, delivery rules, templates, and compliance responsibilities |
| Data governance | The customer is responsible for managing personal data inside its own systems after transfer |
| Custom implementation | This model requires scoping and specific implementation work by the Wiacom team; it is not a self-service configuration |
Model 2 must be agreed and scoped with the Wiacom team before deployment. It cannot be applied retrospectively to an existing Model 1 deployment without data migration and deletion planning.
### When to Consider This Model
This model is well suited for:
* Enterprise or public-sector customers subject to strict data localisation requirements
* Customers who already operate a consolidated CDP or CRM and want to minimise the number of systems holding personal data
* Deployments where a PMS, such as a hotel property management system, is the authoritative system of record for guest identity
* Organisations seeking to reduce the personal-data footprint across third-party processors
* Customers with internal policies requiring privacy-minimised architecture by design
***
## Model Comparison
| | Model 1 — Data Platform / Data Vault | Model 2 — Middleware |
| ------------------------------------- | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ |
| Personal data stored in Wiacom | Yes, with configurable retention; selected data can also be pushed externally | Minimal; pseudonymous identifiers and technical data required to operate the service |
| System of record | Wiacom, or customer system if push-based configuration is used | Customer CRM / CDP / PMS |
| Transactional messaging | Wiacom-provided | Customer-provided |
| API / CDP push available | Optional | Required |
| Analytics and reporting | Full platform analytics available | Limited to pseudonymous and technical session data |
| Implementation type | Standard deployment | Custom scoping required |
| DPA with Wiacom | Required | Required, with reduced processing scope |
| Suitable for strict data minimisation | Partially | Yes |
# Messaging Services
Source: https://docs.wiacom.ai/integrations/messaging
Transactional email and SMS/RCS/WhatsApp delivery — through Wiacom default channels or your own provider.
Wiacom delivers transactional messages as a built-in platform capability. This covers registration confirmation, email verification, WiFi credential delivery, OTP / PIN for phone sign-up, and re-engagement communications (e.g. campaigns).
Two delivery options are available for each deployment.
## Option 1 — Wiacom Default Channels
Wiacom provides managed transactional email and SMS delivery through own channels, configured and operated on the backend.
**Email** is available by default for all deployments, covering:
* Registration confirmation and email verification
* WiFi credential delivery (WiFi Pass passphrases, Key Access passwords)
* Campaign and re-engagement communications
* Guest self-service privacy page links
Sender labelling — by default on Wiacom-owned registered domains, or with a custom sender name and reply-to address — is configurable per deployment.
**SMS and messaging** is available across a broad range of geographies. Wiacom supports major global SMS destinations as well as a number of regional carriers, making coverage available in most major markets. In addition to standard SMS, the following messaging channels are supported:
* **RCS** (Rich Communication Services)
* **WhatsApp**
Messaging delivery covers OTP / PIN for phone-based registration and credential delivery where a messaging channel is configured.
The list of supported destinations and geographies is extensive and restrictions may apply. Contact the Wiacom team to confirm coverage and channel availability for your target region before enabling phone registration flows.
All delivery partners are provisioned and managed on the backend by Wiacom. All integrations are subject to standard security and data handling controls.
## Option 2 — Customer-Provided Services
Customers can connect their own email or SMS/RCS/WhatsApp delivery services instead of, or alongside, Wiacom default channels. This is supported through:
* **API integration** — connect any provider that exposes a standard delivery API
* **Custom service integration** — for customers operating their own internal email or messaging infrastructure
Wiacom already has integrations in place for a large number of major and regional providers. If you are using an established service, there is a good chance it is already supported — contact the Wiacom team to confirm.
When using customer-provided services, the customer is responsible for API credentials, delivery configuration, rate limits, and compliance obligations including sender identification and unsubscribe handling.
## Billing
The platform is billing-ready. Messaging consumption is tracked per deployment and can be managed through prepaid (top-up) or postpaid arrangements. Payment gateway integration is available for deployments where monetised access or paid plan workflows are required. Billing configuration is handled at the account level by the Wiacom team.
# Overview
Source: https://docs.wiacom.ai/integrations/overview
How Wiacom connects to external systems, manages personal data, and supports different data-flow architectures.
Wiacom is designed to operate both as a self-contained data platform and as a connectivity and enforcement layer that feeds into your existing infrastructure.
This section explains how the platform handles personal data, which external systems it can integrate with, and what responsibilities fall on each party depending on the chosen data-flow model.
This content is primarily intended for technical, IT, and compliance stakeholders, including DPOs evaluating data residency and processing responsibilities.
## In This Section
Understand the two supported data-flow architectures — Wiacom as a secure data vault, or Wiacom as privacy-minimised middleware.
Transactional email and SMS delivery — platform-provided or customer-supplied, and when each applies.
Push guest data into your CRM, CDP, PMS, or marketing platform through secure, approved integration channels.
Connect external systems, automate workflows, and consume Wiacom data programmatically via REST API and webhook events.
Local infrastructure appliance for managing WiFi equipment inside management network — deployed as a VM, cloud VM, or bare-metal image.
## Key Principles
Regardless of the integration model in use, the following principles apply across Wiacom deployments:
* Personal data is not transmitted to WiFi vendors or controllers for standard access enforcement. Only technical identifiers, credentials, policy attributes, or pseudonymous values required for authentication and session control are exchanged with the wireless infrastructure.
* All data exposed through the Wiacom API requires strong authentication, and access can be restricted by source IP.
* Personal data is processed only where a valid lawful basis applies, such as consent, service delivery, security, compliance, or other applicable grounds depending on the deployment.
* All platform communication uses HTTPS / TLS 1.2 or higher.
* Wiacom deployments are built on reputable cloud infrastructure providers with independently audited security and compliance programs.
* Hosting regions, infrastructure provider, and data residency requirements are confirmed at deployment time.
## Hosting and Infrastructure Compliance
Wiacom is hosted on reputable cloud infrastructure providers, primarily Microsoft Azure and Google Cloud, depending on the deployment region, customer requirements, and technical architecture.
Amazon Web Services may also be used for selected infrastructure components or customer-specific deployments where required.
These cloud providers maintain extensive security, privacy, and compliance programs, including independent audits and certifications for widely recognised standards ISO/IEC 27001, ISO/IEC 27017, ISO/IEC 27018, SOC 1, SOC 2, SOC 3, CSA STAR, PCI DSS, and GDPR-aligned controls.
Cloud-provider compliance does not replace Wiacom's or the customer's own compliance obligations, but it provides a strong infrastructure foundation for secure and compliant deployments.
At deployment time, Wiacom confirms the applicable hosting region, infrastructure provider, data residency model, and any customer-specific requirements.
Infrastructure compliance documentation, including applicable cloud-provider certifications and audit reports, can be reviewed through the relevant Microsoft, Google, or Amazon trust and compliance portals where available.
The appropriate integration model for your organisation should be agreed with the Wiacom team before deployment, as it affects platform configuration, data processing agreements, and ongoing operational responsibilities.
# Wiacom Agent
Source: https://docs.wiacom.ai/integrations/wiacom-agent
Local appliance for venues where direct cloud-to-infrastructure access is not available.
Wiacom Agent is a managed local appliance that bridges the Wiacom platform with WiFi infrastructure in environments where the controller or AP management interface is not directly reachable from the cloud.
It is deployed inside the customer-controlled network and handles provisioning tasks on behalf of the Wiacom platform. No inbound connectivity is required.
## Deployment Options
Wiacom Agent is available as:
* **VM image** — VMware, Hyper-V, Proxmox, KVM, or VirtualBox
* **Cloud VM image** — inside the customer's own Azure, Google Cloud, or AWS environment
* **Bare-metal image** — on a mini PC, industrial gateway, or similar hardware
Contact [info@wiacom.ai](mailto:info@wiacom.ai) to request more details or a Wiacom Agent for your deployment.
# Introduction
Source: https://docs.wiacom.ai/introduction
Wiacom **Intelligent Connectivity Platform** — documentation hub
Wiacom is a cloud-based WiFi identity, onboarding, engagement, analytics, and operational intelligence platform. It extends the capabilities of existing wireless infrastructure — turning WiFi into a secure, identity-aware layer for venues, enterprises, and multi-site operators — without replacing any hardware.
## Who Uses Wiacom
| Sector | Use Case |
| ------------------------------------- | --------------------------------------------------------------------------------- |
| **Hospitality** | Hotel guest WiFi with PMS integration, VIP recognition, personal SSID via Horizon |
| **Retail** | Shopper WiFi, loyalty linkage, dwell-time analytics |
| **Education** | Student and visitor onboarding with institutional identity verification |
| **Healthcare** | Patient and visitor WiFi with consent capture |
| **Transport hubs** | Airport, station, and transit WiFi with returning-traveller recognition |
| **Enterprise** | Contractor and visitor WiFi separate from the corporate SSID |
| **Residential / serviced apartments** | Resident personal WiFi via Horizon |
| **MSP / Multi-site** | Centralised management across hundreds of locations |
## The Problem Wiacom Solves
Traditional venue WiFi offers two poor options: an open network (no identity, no security) or a shared WPA2 password (minimally secure, anonymous, unmanageable). Neither gives you:
* **Identity** — who is connecting?
* **Consent** — are you GDPR-compliant?
* **Control** — can you revoke access for specific users?
* **Insight** — visit frequency, dwell time, loyalty patterns?
* **Engagement** — can you reach them after they leave?
Wiacom solves all of this while working alongside the WiFi infrastructure you already have.
The platform separates two concerns deliberately:
* **Onboarding** — how a user is registered, identified, and consented
* **Access** — how a validated user is granted WiFi connectivity
A user onboarded through Guest Connect, a Captive Portal, a PMS check-in, a customer app, or any external system via API can then receive access through any of the platform's access features: Portal, WiFi Pass, Key Access, Passpoint Connect, or Horizon — depending on the venue configuration and the WiFi vendor in use.
| Layer | What it does | Examples |
| -------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------- |
| **Onboarding** | Registers and identifies the user, captures consent, triggers the access flow | Guest Connect, Student Connect, Portal registration, PMS check-in, API |
| **Access** | Grants the validated user WiFi connectivity using the method configured for that location | Portal (RADIUS), WiFi Pass (iPSK), Key Access (PSK), Passpoint Connect, Horizon |
## Onboarding Channels
Inline onboarding during the Portal access flow — guests register as they connect
Self-service registration by URL or QR code — email, phone, or social login
Student onboarding with institutional identity verification — coming soon
Staff and contractor onboarding with role-based access — coming soon
Onboard users from any external system — customer apps, web portals, CRM, PMS, and more
## Access Features
Captive portal redirect with RADIUS-based per-user credential authentication for open SSIDs
Unique Personal PSK (iPSK/MPSK/DPSK/other) per registrant — individually revocable and expiry-controlled
Shared WPA2 passphrase delivered to registrants by email, SMS or other channel, with a scannable QR code
Hotspot 2.0 / Passpoint profile-based automatic connection with RADIUS authentication
Cloud WiFi identity orchestration — personal SSIDs, WiFi teleport, and automated provisioning across locations
## Supported WiFi Vendors
| Vendor / Platform | Portal | WiFi Pass | Key Access | API / Provisioning Mode |
| --------------------------------------------------------------- | :----: | :---------------: | :--------: | -------------------------- |
| [Cisco Meraki](/wifi-vendors/cisco-meraki/overview) | ✅ | ✅ | ✅ | Native Cloud API |
| [Cisco WLC](/wifi-vendors/cisco-wlc/overview) | ✅ | — | ✅ | Local Config |
| [HPE Aruba Instant / AOS 8](/wifi-vendors/aruba/overview) | ✅ | Possible | ✅ | Local API / Controller API |
| [HPE Aruba Central / AOS 10](/wifi-vendors/aruba/overview) | ✅ | Licence-dependent | ✅ | Native Cloud API |
| [Ruckus SmartZone / vSZ](/wifi-vendors/ruckus/overview) | ✅ | ✅ | ✅ | Local Config / NBI |
| [UniFi](/wifi-vendors/unifi/overview) | ✅ | Limited | ✅ | Controller API |
| [Cambium cnMaestro / XV](/wifi-vendors/cambium/overview) | ✅ | Vendor-dependent | ✅ | Controller API |
| [Fortinet FortiGate / FortiAP](/wifi-vendors/fortinet/overview) | ✅ | Limited | ✅ | Local Config |
| [MikroTik RouterOS](/wifi-vendors/mikrotik/overview) | ✅ | Limited | ✅ | Router API / Agent |
| [Xirrus / Cambium ArrayOS](/wifi-vendors/xirrus/overview) | ✅ | — | ✅ | Local / Agent |
| [Nomadix](/wifi-vendors/nomadix/overview) | ✅ | — | Limited | Local |
| [OpenWRT / CoovaChilli](/wifi-vendors/openwrt/overview) | ✅ | — | ✅ | Agent / Local Config |
| [TP-Link Omada](/wifi-vendors/tplink/overview) | ✅ | — | ✅ | Local Config |
| [Teltonika](/wifi-vendors/teltonika/overview) | ✅ | Limited | ✅ | Local Config |
| [Huawei WLAN AC](/wifi-vendors/huawei/overview) | ✅ | Vendor-dependent | ✅ | Local Config |
| [EnGenius Cloud](/wifi-vendors/engenius/overview) | ✅ | Vendor-dependent | Depends | Local Config |
| [Draytek Vigor](/wifi-vendors/draytek/overview) | ✅ | — | ✅ | Local Config |
## Get Started
Read [What is Wiacom](/getting-started/what-is-wiacom) and the [Platform Overview](/getting-started/platform-overview).
Follow the [Quick Start](/getting-started/quick-start) to set up a venue.
Pick your vendor and follow its onboarding guide — legacy (manual) or API, depending on the vendor.
Access features, onboarding channels, and equipment integration modes
Talk to the Wiacom team and get your first location set up
Connect your wireless infrastructure to the platform
Connect your first location in minutes
# API & External Platforms
Source: https://docs.wiacom.ai/onboarding/api-platforms
Onboard users into Wiacom from any external system via API
Wiacom exposes a REST API that allows any external system to register users, trigger access workflows, and manage credentials programmatically. This enables onboarding from a customer-built app, a web portal, a loyalty platform, a PMS, a CRM, or any other system — without the user ever interacting with a Wiacom-hosted page.
## Use Cases
| Integration | Description |
| ----------------------------- | ------------------------------------------------------------------------------------------ |
| **Customer mobile app** | Users register or log in inside your own app; the app calls Wiacom to provision access |
| **Web portal** | A venue's existing web portal submits guest registration data to Wiacom on form completion |
| **Hotel PMS** | Check-in event triggers automatic WiFi provisioning for the guest's stay |
| **CRM / loyalty platform** | Known customers are automatically granted access when they arrive at a venue |
| **Staff management system** | Employee onboarding in your HR system simultaneously provisions WiFi access |
| **Event management platform** | Registered attendees receive WiFi credentials as part of the event confirmation |
| **Custom enterprise system** | Any internal system that manages user identity can delegate WiFi access to Wiacom |
## How It Works
Your app, portal, or platform sends a registration event to the Wiacom API — including the user identity information and the target location.
Wiacom creates or updates the user record, applies consent settings, and triggers the access workflow configured for that location.
Depending on the location's configuration, Wiacom provisions a WiFi Pass credential, a Key Access delivery, or a portal authorization — and optionally sends a confirmation to the user.
Registration, access, and lifecycle events are returned via webhook or API response for your system to consume.
## Integration Points
| Method | Description |
| ------------------ | ------------------------------------------------------------------------------------------ |
| **REST API** | Create identities, trigger access workflows, query registration status, manage credentials |
| **Webhooks** | Receive real-time events on registration, re-visit, credential expiry, or revocation |
| **SDK** | Embed Wiacom onboarding flows natively inside iOS or Android apps |
| **PMS connectors** | Native integrations with OPERA Cloud (OHIP) and other property management systems |
## Access Features Available via API
All Wiacom access features are available to API-triggered registrations:
* **Portal** — RADIUS session authorization issued on API registration
* **WiFi Pass** — unique personal passphrase provisioned on the controller and returned via API or email
* **Key Access** — shared passphrase returned via API response or delivered by email
* **Passpoint Connect** — profile delivery triggered on API registration
* **Horizon** — personal SSID provisioned and lifecycle managed via API or PMS event
## Getting Started
API access requires a Wiacom account with API credentials configured. Contact the Wiacom team to receive your API key and endpoint documentation.
Talk to the Wiacom team about API and platform integration
# Captive Portal
Source: https://docs.wiacom.ai/onboarding/captive-portal
Inline onboarding during the Portal access flow
Captive portal onboarding is the inline registration experience that runs as part of the [Portal](/access-features/portal/overview) access flow. Rather than visiting a separate URL, guests encounter the registration form automatically when their browser is redirected by the WiFi controller.
## How It Fits the Platform
Captive portal combines **onboarding** and **access** in a single step:
1. Guest connects to the open SSID
2. Controller redirects HTTP traffic to the Wiacom portal
3. Guest completes the inline registration form
4. Wiacom authenticates via RADIUS and grants access
This is distinct from [Guest Connect](/onboarding/guest-connect/overview), where guests proactively visit a URL or scan a QR code before connecting.
## Registration Options
The captive portal form is fully configurable:
| Mode | Description |
| ---------------------- | -------------------------------------------------------------------------------------- |
| **Registration-free** | Guest clicks to accept terms — instant access. Session and MAC recorded for analytics. |
| **Email registration** | Guest enters name and email. Access granted on submission. |
| **Full registration** | Complete form with all configured fields. Access granted on submission. |
| **Social login** | Guest authenticates via Facebook, Google, Apple, LinkedIn, X, or Microsoft. |
| **Phone / OTP** | Guest enters phone number and receives a PIN by SMS. |
## SDK and App Integration
For organisations that embed WiFi onboarding inside a **mobile app or third-party system**, Wiacom provides an SDK and API that replicates the captive portal flow programmatically:
* **SDK** — integrate the Wiacom onboarding flow inside your iOS or Android app
* **API** — create or validate a guest identity from any external system; Wiacom returns an authorization token that grants access on the controller
This allows onboarding to happen inside your app, a loyalty program, a booking engine, or any other system — with the same RADIUS-based access grant that the captive portal uses.
Contact the Wiacom team to access the SDK documentation or API credentials for programmatic onboarding integration.
## Supported Vendors
Captive portal onboarding is available on all vendors that support external splash page redirect. See the [WiFi Vendors](/wifi-vendors/cisco-meraki/overview) section for vendor-specific configuration.
# Managing Registrations
Source: https://docs.wiacom.ai/onboarding/guest-connect/managing-registrations
View, manage, and integrate guest registrations
## Viewing Registrations
The registrations list is available under **Guest Connect → Registrations** for each location. It provides an overview of registration activity — visit counts, registration timeline, onboarding channel, and status — without exposing personal information in clear text.
All collected data is subject to the customer's data protection strategy, applicable legislation, and the DPO (Data Protection Officer) arrangements in place. Wiacom does not determine the purposes or means of processing — the venue operator is the data controller.
## Managing Access
| Action | Effect |
| ----------- | ------------------------------------------------------------------- |
| **Suspend** | Immediately revokes the user's WiFi access on supported controllers |
| **Restore** | Re-activates a suspended registration |
| **Delete** | Permanently removes the registration record |
For **WiFi Pass** locations, suspending a registration immediately revokes the user's personal passphrase on the controller. For **Key Access** locations, the suspension is recorded in Wiacom but has no network-level effect.
## CRM, CDP, and External Integration
Registration events can be pushed in real time to external systems via:
* **Wiacom REST API** — pull or receive registration and visit events programmatically
* **Webhooks** — push events to any endpoint on registration, re-visit, or status change
* **Native CRM/CDP connectors** — direct integration with supported platforms
Data transmitted to external systems is governed by the customer's own data processing agreements and DPO arrangements. Wiacom does not expose personal data in clear text — all integrations use encrypted transport and are subject to the customer's access control configuration.
## Returning Guests
When a guest registers again using the same identity (email or social profile), Wiacom recognizes them, updates the record, and increments the visit count. No duplicate records are created.
## Privacy and Data Rights
Registered guests receive access to a **self-service privacy page** where they can view their consent record, request data correction, or exercise their right to erasure. This page is provided automatically for all Guest Connect registrations and linked in the confirmation email.
Deletion requests received via the privacy page or submitted directly to the venue operator can be actioned under **Registrations → \[record] → Delete**, which permanently removes the record from Wiacom.
# Guest Connect
Source: https://docs.wiacom.ai/onboarding/guest-connect/overview
Self-service guest registration by URL or QR code
Guest Connect is the primary self-service onboarding channel for public venues. Guests register by visiting a URL or scanning a QR code — without connecting to WiFi first. After registration, Wiacom captures their identity and GDPR consent, then applies the access workflow configured for that location.
## How It Works
A guest arrives at your venue and wants to connect to WiFi.
They visit your Guest Connect URL or scan your QR code and complete the registration form.
Wiacom stores their identity and GDPR consent record.
Wiacom applies the access feature configured for the location — and sends a confirmation email with credentials if applicable (Key Access or WiFi Pass).
On subsequent visits, the guest is recognized by email and their record is updated without creating duplicates.
## What Guest Connect Captures
| Capability | Detail |
| ------------------------------- | ------------------------------------------------------------------------- |
| **Branded registration page** | Customizable logo, colors, headline, and copy |
| **Custom form fields** | Name, email, phone, date of birth, custom dropdowns, and more |
| **GDPR consent** | Required terms and optional marketing consent; full consent record stored |
| **Returning guest recognition** | Recognized by email; visit count incremented; credentials resent |
| **Analytics** | Registration counts, new vs. returning, peak times, source tracking |
| **Guest list and export** | View, search, filter, and export the registered guest database |
## Sign-up Methods
Guest Connect supports all Wiacom identity methods:
* Email sign-up and confirmation
* Phone / OTP (PIN authentication)
* Social login: **Facebook, Google, Apple, LinkedIn, X / Twitter, Microsoft / Azure / Office 365**
* OAuth / SSO
* Pre-registration (admin-created)
* Custom business integrations
## Guest Connect and Access Features
Guest Connect is an onboarding channel — it is independent of the access feature used. After a guest registers through Guest Connect, they receive access via whichever feature is configured for the location:
| Access feature | What the guest receives |
| --------------------- | ------------------------------------------------------------------------------------------------------------ |
| **Key Access** | Confirmation email with the shared WiFi passphrase and QR code |
| **WiFi Pass** | Confirmation email with their unique personal passphrase and QR code |
| **Portal** | RADIUS authorization via auto-generated credentials (if Guest Connect is pre-registration for a portal SSID) |
| **Passpoint Connect** | Passpoint profile delivery |
Guest Connect can also work without a connected WiFi controller — useful for venues that want to collect registrations before their WiFi infrastructure is connected, or where the shared password is managed manually.
## Privacy and Data Rights
After registration, guests receive access to a **self-service privacy page** where they can view, correct, or request deletion of their personal data and consent records. This is provided by Wiacom automatically for all Guest Connect registrations.
## Next Steps
Configure your registration page, form, and email
View, search, export, and manage guest records
# Setting up Guest Connect
Source: https://docs.wiacom.ai/onboarding/guest-connect/setting-up
Configure your Guest Connect registration page, form, and email
## Prerequisites
* A Wiacom account with at least one location created
* (Optional) A WiFi controller or router connected to the location
## Steps
Go to **Guest Connect → Registration Form**.
**Built-in fields:**
| Field | Type | Notes |
| ----------------- | -------- | ---------------------------------------------------- |
| First name | Text | |
| Last name | Text | |
| Email address | Email | Required — used for identity and credential delivery |
| Phone number | Phone | Optional |
| Date of birth | Date | Optional |
| Gender | Dropdown | Optional |
| Marketing consent | Checkbox | Tracked separately from terms |
Click **Add field** to add custom text, dropdown, or checkbox fields.
**GDPR consent checkboxes:**
* **Terms & conditions** — required; blocks submission if unchecked
* **Marketing consent** — optional; tracked separately for campaign targeting
Consent records are stored with timestamp, IP address, and the exact consent text shown at registration. These records are available for export and audit under **Guest Connect → Consent Log**.
Go to **Guest Connect → Sign-up Methods** to enable or disable individual identity methods:
* Email
* Phone / OTP
* Social login (Facebook, Google, Apple, LinkedIn, X, Microsoft)
Social login requires OAuth app credentials configured under **Account → Integrations**.
Go to **Guest Connect → Appearance**:
* Upload your venue logo
* Set brand colors (primary, background, button)
* Edit the page headline and intro text
* Add a background image (optional)
Changes are live immediately after saving.
Go to **Guest Connect → Email** to customize the confirmation email — subject, header, body, and footer.
For **Key Access** locations, Wiacom automatically includes the shared passphrase and QR code in the email. For **WiFi Pass** locations, the email includes the user's unique personal passphrase. If no controller is connected, you can manually enter credential text in the email template.
Go to **Guest Connect → QR Code** to download a print-ready QR code for tables, reception, posters, or digital signage.
# User Onboarding Overview
Source: https://docs.wiacom.ai/onboarding/overview
How Wiacom registers, identifies, and onboards users across all channels
Onboarding is the process by which a user is registered, identified, and consented before receiving WiFi access. Wiacom supports multiple onboarding channels that can operate independently or together at the same location.
Onboarding and access are configured separately. A user onboarded through any channel can receive connectivity via Portal, WiFi Pass, Key Access, Passpoint Connect, or Horizon — independently of how they registered.
## What Onboarding Covers
| Aspect | Detail |
| ------------------- | --------------------------------------------------------------------------- |
| **Identity** | Who the user is — email, phone, social profile, or external system identity |
| **Consent** | GDPR-compliant marketing consent and terms acceptance |
| **Verification** | OTP (SMS/email), social OAuth, or external system validation |
| **Access delivery** | Credentials, passphrase, or QR code sent to the user after registration |
## Registration Methods
Regardless of onboarding channel, users can register using:
* **Email** — sign-up with email address and optional password
* **Phone (OTP)** — PIN authentication via SMS
* **Social / OAuth** — Facebook, Google, Apple, LinkedIn, Twitter/X, Microsoft 365, Azure AD, and other providers
* **Custom integrations** — loyalty programmes, PMS, SSO, CRM, or mobile app SDK
## Onboarding Channels
Registration embedded directly in the WiFi connection flow. Users complete a form before gaining access — no link or QR code required. The most common channel for public and guest WiFi.
A standalone registration page accessed via URL or QR code — independent of the WiFi connection flow. Users can register before arriving, from a poster, or from any device.
Onboarding flow designed for educational environments with institutional identity verification. Coming soon.
Onboarding flow for employees and contractors with role-based access assignment. Coming soon.
Register users programmatically from any external system — mobile apps, PMS, CRM, loyalty platforms, or custom workflows via the Wiacom API.
## Choosing a Channel
| Scenario | Recommended channel |
| ---------------------------------------------------------- | --------------------------------------- |
| Public guest WiFi — users connect and register on the spot | Captive Portal |
| Pre-registration before arrival, or QR code on signage | Guest Connect |
| Campus or school WiFi with student IDs | Student Connect |
| Employee or contractor WiFi | Staff Connect |
| Hotel PMS, loyalty app, or custom mobile app | API & External Platforms |
| Multiple channels at the same location | Any combination — channels are additive |
## How Onboarding Connects to Access
After a user completes registration through any channel, Wiacom delivers their access credentials based on the access features configured for the location:
| Access feature | What the user receives |
| --------------------- | -------------------------------------------------------------------------------- |
| **Portal** | Session credentials handled automatically — user is admitted after registration |
| **WiFi Pass** | A personal passphrase and QR code sent by email |
| **Key Access** | The shared SSID passphrase and QR code sent by email |
| **Passpoint Connect** | A Hotspot 2.0 profile for automatic connection on supported devices |
| **Horizon** | A personal SSID provisioned at the venue for the duration of the stay or session |
For details on each access feature, see [Access Features](/access-features/overview).
# Staff Connect
Source: https://docs.wiacom.ai/onboarding/staff-connect
Staff and contractor onboarding with role-based access — coming soon
Staff Connect is currently in development. Contact [info@wiacom.ai](mailto:info@wiacom.ai) to join the early access program or discuss your requirements.
Staff Connect is a dedicated onboarding channel for employees, contractors, and service staff who require managed WiFi access separate from the corporate network.
## Planned Capabilities
* Role-based access assignment (employee, contractor, temporary staff, seasonal)
* Integration with HR systems, LDAP/Active Directory, and SSO providers
* Pre-registration and batch import from HR rosters
* Automatic de-provisioning on end of contract or employment
* Multi-location access management — staff credentials valid across assigned locations
* Audit trail of access grants, revocations, and policy changes
* Compatible with all Wiacom access features: Portal, WiFi Pass, Key Access, Passpoint Connect, Horizon
## Use Cases
| Use case | Description |
| --------------------- | -------------------------------------------------------------- |
| **Retail staff** | WiFi access for store staff on shared or personal devices |
| **Hospitality staff** | Back-of-house WiFi separate from guest network |
| **Contractor access** | Time-limited WiFi for on-site contractors or service engineers |
| **Multi-site staff** | Single credential valid across all assigned venue locations |
## Current Workaround
Staff onboarding is currently possible using [Guest Connect](/onboarding/guest-connect/overview) with custom form fields, admin-created pre-registrations, or API-based identity creation. Contact the Wiacom team for assisted configuration.
# Student Connect
Source: https://docs.wiacom.ai/onboarding/student-connect
Student onboarding with institutional identity — coming soon
Student Connect is currently in development. Contact [info@wiacom.ai](mailto:info@wiacom.ai) to join the early access program or discuss your requirements.
Student Connect is a dedicated onboarding channel for educational institutions. It provides identity-verified WiFi registration for students with support for institutional authentication systems.
## Planned Capabilities
* Institutional email verification and student ID validation
* Integration with student information systems (SIS) and directory services
* Role-based access (student, faculty, visitor, temporary)
* Bulk enrollment from institution rosters
* Automatic de-provisioning at end of term or enrollment
* GDPR-compliant consent management for students (including minors where applicable)
* Compatible with all Wiacom access features: Portal, WiFi Pass, Key Access, Passpoint Connect
## Use Cases
| Use case | Description |
| --------------------------------- | -------------------------------------------------------------------------- |
| **Campus guest WiFi** | Self-service student registration with institutional identity verification |
| **Temporary lab or event access** | Time-limited credentials for specific spaces or events |
| **Visitor and parent WiFi** | Separate onboarding track for non-students |
| **Student residences** | Horizon-based personal WiFi for student accommodation |
## Current Workaround
Student onboarding is currently possible using [Guest Connect](/onboarding/guest-connect/overview) with custom form fields and email domain validation. Contact the Wiacom team for assisted configuration.
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/aruba/onboarding
Configure Aruba for Wiacom Portal — IAP, Controller, and Instant On
RADIUS server details and portal URL are region-specific. Obtain the correct values from the Wiacom admin panel or the Wiacom team before starting.
## Step 1 — Add the Device to Wiacom
1. Go to **Inventory → Routers → Add New Router**
2. Select **Aruba** from the vendor dropdown
3. Enter the required details and assign a location
4. Click **Save**
Log in to your Aruba IAP (Master AP).
## Create the SSID
Under **Network** at the top left, click **New**:
* Name (SSID): your guest WiFi name
* Primary usage: **Guest**
Click **Next**:
* Client IP assignment: Virtual Controller managed
* Client VLAN assignment: Default (or your guest VLAN)
Click **Next** and configure the splash page:
* Splash page type: **External**
* Captive portal profile: click the dropdown → **New**
* Name: `guestwifi`
* Type: **Radius Authentication**
* IP or hostname: `` — provided by Wiacom
* URL: `` — provided by Wiacom
* Port: `443`
* Use HTTPS: Enabled
* Redirect URL: `?res=success`
## Configure RADIUS Auth Servers
Auth server 1:
* Type: RADIUS, Name: `guestwifi1`
* IP address: ``
* Auth port: `1812`, Acct port: `1813`
* Shared key: ``
Auth server 2:
* Type: RADIUS, Name: `guestwifi2`
* IP address: ``
* Auth port: `1812`, Acct port: `1813`
* Shared key: ``
Additional settings:
* Reauth interval: `24 hrs`
* Accounting: Enabled, Accounting mode: Authentication, Interval: `3 min`
## Configure Walled Garden
Click **"Blacklist: 0 Whitelist: 0"** and add domains one by one:
```
*.wiacom.ai
*.akamaitechnologies.com
*.akamaiedge.net
*.akamaized.net
*.akamai.net
*.amazonaws.com
*.fastly.net
*.zencdn.net
fast.wistia.com
player.vimeo.com
*.facebook.com
*.fbcdn.net
*.akamaihd.net
connect.facebook.net
*.instagram.com
*.twitter.com
*.twimg.com
*.linkedin.com
*.licdn.net
*.licdn.com
*.google.com
*.googleapis.com
*.gstatic.com
```
## Configure Access Rules
Click **Next** → Access Rules: **Role-based**
Under Roles, click **New** → name `Preauth`
Under Access Rules for Preauth, click **New** for each walled garden domain:
* Rule type: Access control
* Service: Network - any
* Action: Allow
* Destination: To domain name
* Domain name: `*insert domain here*`
Assign pre-authentication role: select **Preauth**
Click **Finish**.
Log in to your Aruba Controller web interface.
## Create the WLAN
Click **Configure → WLANs → +**:
* Name (SSID): your guest WiFi name
* Primary Usage: **Guest**
* Forwarding Mode: Tunnel
Click **Next** → VLAN: your guest VLAN
Click **Next**:
* Is this WLAN for internal or guest? **Guest**
Click **Next**:
* Captive Portal Type: **ClearPass or other external Captive Portal**
## Configure RADIUS
Under Auth servers, click **+ → +** to create new servers:
Server 1:
* Server type: RADIUS, Name: `guestwifi1`
* IP Address: ``
* Auth port: `1812`, Accounting port: `1813`
* Shared key: ``
Server 2:
* Name: `guestwifi2`
* IP Address: ``
* Auth port: `1812`, Accounting port: `1813`
* Shared key: ``
Under **Advanced Settings**:
* Called Station ID Type: MAC Address
* Called Station ID Include SSID: Enabled
* Accounting: Use authentication servers, Interval: `4 min`
## Configure Walled Garden (Allowlist)
Under Allowlist, click **+ Add** and add each domain from the list above.
## Configure Access Rules
Click **Next** → Access rules: **Role Based**
Click **Add Role** → name `Preauth`
For each walled garden domain, add a rule:
* Access Control / Network / Any / Allow / To a Domain Name: `*domain*`
Add a final deny rule:
* Access Control / Network / Any / Deny / To All Destinations (must be last)
Configure:
* Captive Portal Profile: your portal profile
* Assign Pre-Authentication Role: `Preauth`
Click **Finish**.
Log in to the Aruba Instant On portal at [portal.arubainstanton.com](https://portal.arubainstanton.com).
Aruba Instant On does not support RADIUS authentication. Wiacom analytics features (online users, network reports) and tiered bandwidth are unavailable.
## Create the Network
Click **Networks → Add a new network**:
* Network Name: your guest WiFi name
* Network type: **Guest**
Click **Save**.
## Configure the Guest Portal
Click **Customize guest portal**:
* Portal type: **External**
* Server URL: `` — provided by Wiacom
* Redirect URL: `?res=success`
* Whitelisted domains: add all domains from the walled garden list above
* Send RADIUS Accounting: Enabled
* Primary RADIUS Server IP: ``
* Primary RADIUS Server Secret: ``
* Secondary RADIUS Server: Enabled
* Secondary RADIUS Server IP: ``
* Secondary RADIUS Server Secret: ``
Click **Apply changes**.
## Troubleshooting
Confirm the SSID is set to Guest type and the splash page type is External. Check that HTTP (not HTTPS) pages trigger the redirect.
Verify RADIUS server addresses and shared secret match values from Wiacom. Confirm UDP 1812 and 1813 are reachable.
Ensure the relevant social provider domains are in the walled garden.
# Aruba
Source: https://docs.wiacom.ai/wifi-vendors/aruba/overview
Wiacom Portal integration with Aruba wireless — IAP, Controller, and Instant On
Wiacom integrates with Aruba wireless infrastructure in three hardware variants. All support Portal access via external splash page and RADIUS. WiFi Pass (iPSK) is supported on Aruba controller and IAP deployments.
## Supported Access Features
| Feature | Supported |
| ---------- | -------------------------------------------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | ✅ (Aruba IAP and Controller; not Instant On) |
## Hardware Variants
| Variant | Description |
| ----------------------- | ------------------------------------------------------- |
| **Aruba IAP / Instant** | Standalone access points with virtual controller |
| **Aruba Controller** | Centralised mobility controller managing APs |
| **Aruba Instant On** | Cloud-managed SMB APs — RADIUS accounting not supported |
Aruba Instant On does not support RADIUS authentication and accounting. Some Wiacom analytics features (online users, network reports) and tiered bandwidth are unavailable on Instant On.
Step-by-step configuration for all Aruba variants
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/cambium/onboarding
Configure Cambium cnPilot Enterprise AP for Wiacom Portal
Firmware 3.1 or above required. RADIUS details and portal URL are region-specific — obtain from Wiacom before starting.
## Step 1 — Add the Device to Wiacom
1. Go to **Inventory → Routers → Add New Router**
2. Select **Cambium / cnPilot** from the vendor dropdown
3. Enter required details and assign a location
4. Click **Save**
## Step 2 — Create the WLAN
Log in to the AP web interface. Go to **Configure → WLAN → Create Wireless LAN** (top right).
**Basic tab:**
| Field | Value |
| ---------------- | ------------------------ |
| Enable | Enabled |
| SSID | Your guest WiFi name |
| VLAN | Your guest VLAN (or `1`) |
| Security | `open` |
| Radios | 2.4 GHz and 5 GHz |
| Max Clients | 200 |
| Client Isolation | Enabled |
Click **Save**.
## Step 3 — Configure RADIUS
**Radius Server tab:**
| Field | Value |
| ------------------------------ | ------------------------ |
| Authentication Server 1 Host | `` |
| Authentication Server 1 Port | `1812` |
| Authentication Server 1 Secret | `` |
| Authentication Server 2 Host | `` |
| Authentication Server 2 Port | `1812` |
| Authentication Server 2 Secret | `` |
| Accounting Server 1 Host | `` |
| Accounting Server 1 Port | `1813` |
| Accounting Server 2 Host | `` |
| Accounting Server 2 Port | `1813` |
| Accounting Mode | `start-interim-stop` |
| Server Pool Mode | Failover |
| Interim Update Interval | `120` |
Click **Save**.
## Step 4 — Configure Guest Access (Portal)
**Guest Access tab:**
| Field | Value |
| ------------------ | ----------------------------------- |
| Enable | Enabled |
| Portal Mode | External Hotspot |
| Access Policy | RADIUS |
| Redirect Mode | HTTP |
| External Page URL | `` — provided by Wiacom |
| Success Action | Redirect user to External URL |
| Redirect URL | `?res=success` |
| Session Timeout | `86400` |
| Inactivity Timeout | `1800` |
Click **Save**.
## Step 5 — Configure Walled Garden
Under **Add White List**, add each domain one at a time:
```
*.wiacom.ai
*.akamaitechnologies.com
*.akamaiedge.net
*.akamaized.net
*.akamai.net
*.amazonaws.com
*.fastly.net
*.zencdn.net
fast.wistia.com
player.vimeo.com
*.facebook.com
*.fbcdn.net
*.akamaihd.net
connect.facebook.net
*.instagram.com
*.twitter.com
*.twimg.com
*.linkedin.com
*.licdn.net
*.licdn.com
```
Add any additional domains used in your portal customization.
## Troubleshooting
Confirm Portal Mode is set to External Hotspot and Redirect Mode is HTTP. Check that Client Isolation is enabled.
Verify server addresses and shared secret. UDP 1812 and 1813 must be reachable.
# Cambium
Source: https://docs.wiacom.ai/wifi-vendors/cambium/overview
Wiacom Portal integration with Cambium cnPilot Enterprise APs
Wiacom integrates with Cambium Networks cnPilot Enterprise APs using external hotspot (Guest Access) with RADIUS authentication. Firmware version 3.1 or above is required.
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — |
## Requirements
* Cambium cnPilot AP, firmware 3.1 or above
* RADIUS server details and portal URL from Wiacom for your region
* A Wiacom account with a location created
Step-by-step configuration for Cambium cnPilot Enterprise AP
# Horizon
Source: https://docs.wiacom.ai/wifi-vendors/cisco-meraki/horizon-access
Personal WiFi identity for Cisco Meraki.
Horizon is Wiacom's cloud WiFi identity orchestration layer. It enables personal WiFi experiences across locations — provisioning individual SSIDs or credentials per user and managing their full lifecycle automatically.
Rather than connecting to a shared guest network, each user receives their own named WiFi network provisioned at the venue for the duration of their stay or session.
## Prerequisites
* **API Mode enabled** , controller added on Wiacom Platform and assigned to location.
* Meraki API key with **Read + Write** permissions at organisation level
* Minimum one available "Unconfigured" SSID who will be reserved and used for Horizon service provisioning.
Follow Onboarding process from [Add the Meraki controller](/wifi-vendors/cisco-meraki/onboarding#api-add-controller)
Nothing should be configured on Meraki side. Just take a note of SSID number who will be assigned to Horizon service. Meraki SSID orders start from 0 to 14 and *Unconfigured* state is recommended.
Contact [info@wiacom.ai](mailto:info@wiacom.ai) for more info or to plan a Horizon deployment.
# Key Access
Source: https://docs.wiacom.ai/wifi-vendors/cisco-meraki/key-access
Shared WPA2 passphrase delivery on Cisco Meraki
Key Access on Meraki stores a shared WPA2 passphrase in Wiacom, delivers it to registered users by email with a QR code, and (in API mode) pushes it to the Meraki SSID automatically.
## SSID Settings
| Setting | Value |
| ----------- | ---------------------------------------------------------- |
| Security | WPA2 Personal |
| Splash page | None (direct access) - Ask Wiacom if you want to enable it |
## API Mode
Enter the passphrase in Wiacom — it is pushed to the Meraki SSID automatically and updated instantly when changed.
## Manual Configuration (Legacy / Non-API Mode)
If you connected Wiacom via the Meraki API, SSID configuration is pushed automatically — skip this section.
Enter the passphrase in Wiacom. Wiacom stores it securely and delivers it to registered users by email and QR code. You must also apply the same passphrase to the SSID manually in the Meraki Dashboard — Wiacom cannot push it without an API connection.
Log in to [dashboard.meraki.com](https://dashboard.meraki.com), navigate to **Wireless → Access Control**, and select your SSID.
| Setting | Value |
| ----------- | -------------------------------------------------------- |
| Security | Password |
| Passphrase | Enter the passphrase defined in Wiacom for this location |
| Splash page | None (direct access) |
Click **Save Changes**.
Optional, follow [this procedure](/wifi-vendors/cisco-meraki/onboarding#manual-mode) for adding Meraki devices into the Wiacom platform.
## Updating the Passphrase
Go to **Inventory → Controllers → \[controller] → \[SSID row] → Edit**, enter the new passphrase, and save. In API mode, Wiacom pushes the change to Meraki immediately. In legacy mode, update the SSID passphrase in the Meraki Dashboard separately to keep it in sync.
Changing the passphrase disconnects all currently connected devices. All users must reconnect with the new passphrase.
For individual, revocable credentials, use [WiFi Pass](/wifi-vendors/cisco-meraki/wifi-pass) instead.
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/cisco-meraki/onboarding
Add a Cisco Meraki controller to Wiacom — legacy and API modes
Choose the integration mode that suits your deployment.
API mode connects Wiacom to your Meraki Dashboard. Wiacom discovers your networks and SSIDs, assigns feature roles, and pushes all SSID configuration automatically.
## Prerequisites
* Meraki organisation with at least one wireless network and MR access points
* Dashboard API access enabled at **Organization → Settings → Dashboard API access**
* Meraki API key with **Read + Write** permissions at organisation level
* RADIUS Accounting enabled on the organisation (contact Cisco Meraki support if unavailable)
In the Meraki Dashboard: account email (top-right) → **My Profile** → **API access** → **Generate new API key**. Copy it immediately — shown only once.
## Step 1 — Prepare SSIDs in Meraki Dashboard
Create one SSID per access feature you want to use. All three can run on the same network using separate SSIDs.
| Feature | Security setting | Splash page |
| -------------- | ----------------------------- | ------------------------ |
| **Portal** | Open or Open (Enhanced / OWE) | Any custom splash option |
| **WiFi Pass** | Identity PSK without RADIUS | None (direct access) |
| **Key Access** | WPA2 Personal | None (direct access) |
SSIDs named *Unconfigured* are excluded from detection — rename any SSID you want Wiacom to manage before connecting.
**Client IP and VLAN** should be set according to your network requirements.
For **WiFi Pass**, ensure at least one **Group Policy** exists in the network (**Network → Group Policies**) — Meraki requires this for iPSK creation.
Portal and WiFi Pass cannot share the same SSID. Use separate SSIDs if you need both.
## Step 2 — Add the Controller in Wiacom
From the Admin dashboard:
1. Go to **Inventory → Controllers → Add controller → Cisco Meraki**
2. Enter a label (e.g. *Meraki – Main Controller*)
3. Paste your Meraki API key and click **Next**
Loading may take longer for organisations with many networks, SSIDs, and APs. Meraki enforces a 5 req/sec API rate limit.
## Step 3 — Select Organisation
Choose the Meraki organisation to link and click **Next**. Wiacom fetches all wireless-capable networks and eligible SSIDs. SSIDs named *Unconfigured* are excluded automatically.
## Step 4 — Assign SSID Roles
Map each SSID to a Wiacom feature role. One SSID maps to one role. One network maps to one location.
| Role | Effect |
| -------------- | -------------------------------------------------------- |
| **Portal** | Wiacom pushes splash URL and RADIUS settings to the SSID |
| **WiFi Pass** | Wiacom provisions iPSKs on this SSID via the Meraki API |
| **Key Access** | Wiacom stores and pushes the shared passphrase |
## Step 5 — Map Networks to Locations
Assign each Meraki network to a Wiacom venue location. Click **Finish**.
Wiacom saves the configuration, pushes SSID settings to Meraki, and imports the AP inventory.
## After Setup
| Action | Where |
| ---------------------------- | -------------------------------------------------------------- |
| Sync latest topology | **Inventory → Controllers → Sync from controller** |
| Enable / disable SSIDs | Toggle in the SSID table |
| Update Key Access passphrase | Edit icon on the Key Access SSID row |
| Set bandwidth limits | **BW** icon on any SSID row |
| Configure WiFi Pass expiry | Clock icon on the WiFi Pass SSID row |
| Rotate API key | **Inventory → Controllers → \[controller] → Edit credentials** |
For full details on managing controllers, see [Controllers](/admin-reference/controllers).
## Troubleshooting
Confirm Dashboard API access is enabled under **Organization → Settings** and the key was copied without trailing spaces.
Ensure at least one SSID is enabled and named in Meraki. SSIDs named *Unconfigured* are hidden automatically.
Confirm the SSID is set to *Identity PSK without RADIUS* and at least one Group Policy exists in **Network → Group Policies**.
Ensure RADIUS Accounting is enabled. Contact Cisco Meraki support if the option is unavailable in your Dashboard.
Legacy mode does not require API access. SSIDs are configured directly in the Meraki Dashboard; devices are registered in Wiacom manually. Portal, iPSK with RADIUS, and Key Access are supported. iPSK without RADIUS is not available in legacy mode.
## Step 1 — Configure the SSID in Meraki
Configure the SSID in the Meraki Dashboard according to the feature you are deploying. Full field-by-field instructions are on each feature page:
Open SSID with RADIUS splash — Access Control, RADIUS servers, Splash Page settings
Identity PSK with RADIUS — Access Control and RADIUS server settings
WPA2 Personal — apply the passphrase set in Wiacom to the SSID
## Step 2 — Register the Device in Wiacom
Once the SSID is configured in Meraki, add the access point or router to Wiacom:
From the Admin dashboard:
1. Go to **Inventory → Routers → Add New Router**
2. Select **Cisco Meraki** as the vendor
3. Enter the required network identifier details
4. Assign a location and click **Save**
For deployments with multiple devices, Wiacom supports bulk import via CSV. See [Inventory Management](/admin-reference/inventory) for import instructions and field requirements.
For full details on managing inventory, see [Inventory](/admin-reference/inventory).
# Overview
Source: https://docs.wiacom.ai/wifi-vendors/cisco-meraki/overview
Wiacom integration with Cisco Meraki MR wireless networks
Integration can be done via the Meraki Dashboard API v1 named **API mode** or via direct device configuration without API access, named **Manual or legacy mode**. The integration covers controller onboarding, SSID configuration, per-user credential provisioning, real-time enforcement, and credential lifecycle management.
## Supported Access Features
| Feature | SSID mode on Meraki | API required for operation | API config support | Legacy/Manual config |
| ----------------------------------- | ----------------------------------- | :------------------------: | :----------------: | :------------------------------------------------------------------------------: |
| **Portal** | Open / Open-Enhanced + RADIUS | No | ✅ | ✅ Manual SSID config |
| **WiFi Pass** (iPSK without RADIUS) | Identity PSK without RADIUS | ✅ | ✅ | — |
| **WiFi Pass** (iPSK with RADIUS) | Identity PSK with RADIUS (Easy PSK) | No | ✅ | ✅ Manual SSID config |
| **Key Access** | WPA2 Personal | No | ✅ | ✅ Manual SSID config + PSK in Wiacom |
| **Passpoint Connect** | MAC-based Auth/Hotspot 2.0 | No | No | ✅ Manual SSID config according to Wiacom |
| **Horizon** | WPA2 Personal | ✅ | No | ✅ Manual SSID slots should be added on Wiacom, no config required on Meraki side |
All features can run simultaneously on the same Meraki network using separate SSIDs.
## Integration Modes
**API mode (recommended):** Wiacom connects to the Meraki Dashboard API, discovers all networks and SSIDs, assigns feature roles, and pushes all SSID configuration automatically.
**Legacy / manual mode:** SSID configuration is performed directly in the Meraki Dashboard. APs are imported manually into Wiacom. Portal requires manual splash URL and RADIUS setup. iPSK with RADIUS is supported with manual SSID configuration.
## Requirements
| Requirement | Detail |
| ------------------------------ | ----------------------------------------------------------------------------------------------- |
| Firmware — Portal / Key Access | MR 29.4.1 or later |
| Firmware — WiFi Pass | MR 30.1 or later |
| Dashboard API access | Enabled at **Organization → Settings → Dashboard API access** (API mode only) |
| API key permissions | Read + Write at organisation level (API mode only) |
| WiFi Pass hardware | Wi-Fi 5 Wave 2 or newer — see [requirements](/wifi-vendors/cisco-meraki/wifi-pass#requirements) |
| RADIUS Accounting | Must be enabled — request via Cisco Meraki support if unavailable |
## Pages in This Section
Add a Meraki controller or AP to Wiacom — API and manual modes
Captive portal configuration on Meraki
Per-user Identity PSK provisioning
Shared passphrase delivery via email and QR code
Hotspot 2.0 / Passpoint profile-based automatic WiFi access
Personal WiFi identity orchestration
# Passpoint / Hotspot 2.0
Source: https://docs.wiacom.ai/wifi-vendors/cisco-meraki/passpoint-access
Hotspot 2.0 configuration on Cisco Meraki Dashboard
On Cisco Meraki MR, Passpoint is configured as Hotspot 2.0.
Only Manual config mode is supported. For multiple locations environments, API support can be added
### Access Control
Log in to [dashboard.meraki.com](https://dashboard.meraki.com), navigate to **Wireless → Access Control**, and select your SSID from the dropdown.
| Setting | Value |
| ------------------ | ------------------------------------- |
| SSID status | Enabled |
| SSID (name) | Set a name according to your set-up |
| Security | Enterprise with "my Radius server" |
| Splash page | None |
| Client IP and VLAN | As preffered, per your network config |
### RADIUS Authentication Servers
Under **RADIUS**, click **Add server** and add two entries:
| # | Host | Auth Port | Secret |
| - | ------------------- | --------- | ------------------------ |
| 1 | `` | 1812 | `` |
| 2 | `` | 1812 | `` |
### RADIUS Accounting Servers
Under **RADIUS accounting**, click **Add server** and add two entries:
| # | Host | Accounting Port | Secret |
| - | ------------------- | --------------- | ------------------------ |
| 1 | `` | 1813 | `` |
| 2 | `` | 1813 | `` |
Set **Accounting interim interval** to **2 minutes**.
### Advanced RADIUS Settings
If the **Advanced RADIUS settings** section is present, configure:
| Setting | Value |
| ----------------- | ---------------------------------- |
| Called-Station-ID | AP MAC address (remove any others) |
| NAS ID | remove any others |
| Server timeout | 5 seconds |
| Retry count | 3 |
Click **Save Changes**.
### Hotspot 2.0
Navigate to **Wireless → Hotspot 2.0** and from SSID dropdown select previously create SSID name
Domain List, Roaming Consortium, NAI realms are design specific - Ask Wiacom before for details
| Setting | Value |
| --------------------- | --------------------------------------- |
| Hotspot 2.0 | Enabled |
| Operator name | Wiacom |
| Venue name | `Your venue name` |
| Venue type | Unspecified (unless specified ) |
| Network type | Free public network (unless specified ) |
| Domain list | `` |
| Roaming Consotium OIs | `` |
| NAI Realms | `` |
| MCC/MNCs | Leave empty |
Click **Save Changes**.
# Portal
Source: https://docs.wiacom.ai/wifi-vendors/cisco-meraki/portal
Captive portal configuration on Cisco Meraki Dashboard
Portal on Meraki uses an open SSID with a Wiacom splash URL and RADIUS-based per-session authentication. When a guest connects and opens a browser, Meraki redirects them to the Wiacom portal.
**API mode users:** If you integrated Wiacom via the Meraki API, all SSID settings — splash URL, RADIUS servers, and walled garden — are pushed automatically. No manual configuration is required. You can skip to [Walled Garden](#walled-garden) if you need to add social login providers or whitelist other destinations.
## Authentication Model
Wiacom uses **per-session generated credentials** for RADIUS authentication — not the guest's MAC address. A unique username and password are generated for each portal session and sent to the Wiacom RADIUS server.
## Manual Configuration (Legacy / Non-API Mode)
If you are not using API mode, configure the SSID manually in the Meraki Dashboard as follows.
Portal URL, RADIUS server details, and shared secrets are region-specific. Obtain all values from the Wiacom admin panel or the Wiacom team before proceeding.
### Access Control
Log in to [dashboard.meraki.com](https://dashboard.meraki.com), navigate to **Wireless → Access Control**, and select your SSID from the dropdown.
| Setting | Value |
| ------------------------------------------------------------- | --------------------------------------------------- |
| SSID status | Enabled |
| Security | Open (no encryption) |
| Splash page | Sign-on with "my RADIUS server" |
| Advanced splash settings > Captive portal strength | Block all access until sign-on is complete |
| Advanced splash settings > Walled garden | Enabled — see [Walled Garden](#walled-garden) below |
| Advanced splash settings > Simultaneous logins | Allow |
| Advanced splash settings > Controller disconnection behaviour | Default |
| Client IP and VLAN | As preffered, per your network config |
### RADIUS Authentication Servers
Under **RADIUS**, click **Add server** and add two entries:
| # | Host | Auth Port | Secret |
| - | ------------------- | --------- | ------------------------ |
| 1 | `` | 1812 | `` |
| 2 | `` | 1812 | `` |
### RADIUS Accounting Servers
Under **RADIUS accounting**, click **Add server** and add two entries:
| # | Host | Accounting Port | Secret |
| - | ------------------- | --------------- | ------------------------ |
| 1 | `` | 1813 | `` |
| 2 | `` | 1813 | `` |
Set **Accounting interim interval** to **4 minutes**.
### Advanced RADIUS Settings
If the **Advanced RADIUS settings** section is present, configure:
| Setting | Value |
| ----------------- | ---------------------------------- |
| Called-Station-ID | AP MAC address (remove any others) |
| NAS ID | remove any others |
| Server timeout | 5 seconds |
| Retry count | 3 |
Click **Save Changes**.
### Splash Page
Navigate to **Wireless → Splash Page** and configure:
| Setting | Value |
| -------------------------------------------- | -------------------------------------------------------------------------------- |
| Custom splash URL | `` |
| Where should users go after the splash page? | The URL they were trying to fetch, or a specific redirect URL provided by Wiacom |
Click **Save Changes**.
## Walled Garden
The walled garden allows unauthenticated devices to reach the portal and social login providers before completing sign-on. In API mode this is configured automatically. In legacy mode, add the following domains under **Wireless → Splash Page → Walled garden**:
| Category | Domains |
| -------------------- | ---------------------------------------------------------------------------------------------------- |
| **Required** | `*.wiacom.ai` , `*.wiacom.io` |
| CDN | `*.akamaitechnologies.com`, `*.akamaiedge.net`, `*.akamaized.net`, `*.amazonaws.com`, `*.fastly.net` |
| Facebook / Instagram | `*.facebook.com`, `*.fbcdn.net`, `*.akamaihd.net`, `connect.facebook.net`, `*.instagram.com` |
| Google | `accounts.google.com`, `*.googleapis.com`, `*.gstatic.com` |
| Twitter / X | `*.twitter.com`, `*.twimg.com` |
| LinkedIn | `*.linkedin.com`, `*.licdn.net`, `*.licdn.com` |
Please note, other Walled Garden entries may be requiered - Ask Wiacom for details
## Troubleshooting
Confirm the SSID is set to Open and a custom splash option is selected. Try `http://neverssl.com` — HTTPS traffic is not intercepted by the captive portal mechanism.
Check RADIUS Accounting is enabled at the Meraki organisation level. In legacy mode, verify the RADIUS server addresses and shared secret match what was provided by Wiacom. In API mode, check the RADIUS settings pushed by Wiacom under **Inventory → Controllers → \[SSID row]**.
Ensure the relevant social provider domains are present in the Meraki splash walled garden. In API mode, Wiacom pushes the core walled garden — social login domains may need to be added manually if not already present.
# WiFi Pass
Source: https://docs.wiacom.ai/wifi-vendors/cisco-meraki/wifi-pass
Per-user Identity PSK provisioning on Cisco Meraki
WiFi Pass support both Meraki's **Identity PSK without RADIUS** and **Identity PSK with RADIUS (Easy PSK)** features integration. Each registrant receives a unique personal passphrase provisioned on the SSID via the Meraki iPSK API (for ipsk-without-radius) or pushed directly to RADIUS (ipsk-with-radius).
## Requirements
Requires **Wi-Fi 5 Wave 2 or newer** access points:
| Generation | Supported Models |
| -------------- | ------------------------------------------------------------------------ |
| Wi-Fi 5 Wave 2 | MR20, MR30H, MR33, MR42, MR42E, MR52, MR53, MR53E, MR70, MR74, MR84 |
| Wi-Fi 6 | MR28, MR36, MR36H, MR44, MR46, MR46E, MR56, MR76, MR78, MR86, MR45, MR55 |
| Wi-Fi 6E | MR57, CW9162I, CW9164I, CW9166I |
Older MR access points (Wi-Fi 4 / Wi-Fi 5 Wave 1) do not support Identity PSK. All APs in the network must meet the minimum hardware and firmware requirements.
* Meraki firmware **MR 30.1 or later** on all APs
* At least one **Group Policy** configured in the network (**Network → Group Policies**)
* Available SSID
* API mode required when ipsk-without-radius is used
## Guest Experience
User registers via any [onboarding channel](/onboarding/overview).
A unique passphrase is created for the SSID.
The SSID and passphrase are delivered to the user. The QR code allows one-tap connection on supported devices. These details can optionally be shown on-screen at registration time and sent through one of the enabled communication channels. See [Messaging Services](/integrations/messaging).
User connects using standard WPA2 — no app, no profile required.
## Limits
For deployments exceeding 5,000 credentials, Identity PSK with RADIUS (Easy PSK) should be used.
## Manual Configuration (Legacy / Non-API Mode)
Only **Identity PSK with RADIUS (Easy PSK)** is supported in legacy mode.
If you connected Wiacom via the Meraki API, SSID configuration is pushed automatically — skip this section.
RADIUS server FQDN/addresses, ports and shared secrets are region-specific. Obtain all values from the Wiacom admin panel or the Wiacom team before proceeding.
Log in to [dashboard.meraki.com](https://dashboard.meraki.com), navigate to **Wireless → Access Control**, and select your SSID.
### Access Control
| Setting | Value |
| ------------------ | ---------------------------------------------------------- |
| SSID status | Enabled |
| Security | Identity PSK with RADIUS (Easy PSK) |
| Splash page | None (direct access) - Ask Wiacom if you want to enable it |
| Client IP and VLAN | As preffered, per your network config |
### RADIUS Authentication Servers
Under **RADIUS**, click **Add server** and add two entries:
| # | Host | Auth Port | Secret |
| - | ------------------- | --------- | ------------------------ |
| 1 | `` | 1812 | `` |
| 2 | `` | 1812 | `` |
Click **Save Changes**.
Follow [this procedure](/wifi-vendors/cisco-meraki/onboarding#manual-mode) for adding Meraki devices into the Wiacom platform.
## Troubleshooting
Ensure the SSID is set to *Identity PSK without RADIUS* and at least one Group Policy exists in **Network → Group Policies**.
Check the credential is not suspended or expired under **WiFi Pass → Credentials**.
Check the expiry timestamp in the credential record. The user can re-register to receive a new passphrase.
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/cisco-wlc/onboarding
Configure Cisco WLC for Wiacom Portal
RADIUS details and portal URL are region-specific — obtain from Wiacom before starting. Collect the Base Radio MAC address of each AP and send to the Wiacom team before proceeding.
## Step 1 — Add the Device to Wiacom
1. **Inventory → Routers → Add New Router**
2. Select **Cisco WLC**, fill in details (including AP Base Radio MACs), assign a location, click **Save**
## Step 2 — Configure RADIUS for Authentication
**SECURITY → AAA → RADIUS → Authentication → New**
Setup RADIUS Attributes Format:
| Field | Value |
| --------------------------- | -------------- |
| Auth Called Station ID Type | AP MAC Address |
| MAC Delimiter | Hyphen |
Create authentication server:
| Field | Value |
| -------------------- | ------------------------ |
| Server Address | `` |
| Port Number | `1812` |
| Shared Secret Format | ASCII |
| Shared Secret | `` |
## Step 3 — Configure RADIUS for Accounting
**SECURITY → AAA → RADIUS → Accounting → New**
Same format settings as above. Create accounting server:
| Field | Value |
| -------------- | ------------------------ |
| Server Address | `` |
| Port Number | `1813` |
| Shared Secret | `` |
## Step 4 — Configure Access Control Lists (Walled Garden)
Create ACLs to permit unauthenticated clients to reach the Wiacom portal and social login providers.
**For Access Points NOT in FlexConnect mode** — use DNS-based ACLs with the following domains:
```
Wiacom portal: *.wiacom.ai
Facebook: *.facebook.com, *.fbcdn.net, *.akamaihd.net, connect.facebook.net
Instagram: *.instagram.com
Twitter/X: *.twitter.com, *.twimg.com
LinkedIn: *.linkedin.com, *.licdn.net, *.licdn.com
Google: *.google.com, *.googleapis.com, *.gstatic.com
CDN: *.akamaitechnologies.com, *.akamaiedge.net, *.akamaized.net, *.amazonaws.com, *.fastly.net
```
**For Access Points in FlexConnect mode** — only IP-based ACLs are supported. Use the IP list provided by Wiacom for your region.
## Step 5 — Configure Portal Login and WLAN
**SECURITY → Web Auth → Web Login page**:
* Redirect URL after login: leave blank
**Controller → Interfaces**: check the virtual interface IP (adjust to a non-public IP if needed)
**Management → HTTP-HTTPS**:
* WebAuthSecureWeb: Disabled
* HTTPS Redirection: Disabled
(Reboot may be required)
**From CLI** (cannot be done via web interface, reboot may be required):
```
config custom-web logout-popup disable
config network web-auth captive-bypass
```
**WLANs → Create New → Go**:
| Section | Field | Value |
| ------------------ | ----------------------- | --------------------------------------- |
| General | SSID | Your guest WiFi name |
| Security > Layer 2 | Layer 2 Security | None |
| Security > Layer 3 | Layer 3 Security | Web Policy |
| | Authentication | Enabled |
| | Pre-authentication ACL | Your ACL name |
| | Override Global Config | Enabled |
| | Web Auth type | External (Re-direct to external server) |
| | Redirect URL | `` |
| Security > AAA | Authentication Servers | Enabled, `` port 1812 |
| | Accounting Servers | `` port 1813 |
| | Interim Update | Enabled, Interval: 600 |
| | Authentication priority | RADIUS |
| Advanced | Allow AAA Override | Enabled |
| | Enable Session Timeout | Enabled, 1800 secs |
## Troubleshooting
Confirm WebAuthSecureWeb and HTTPS Redirection are both disabled. The CLI commands (`captive-bypass` and `logout-popup disable`) may require a reboot to take effect.
Verify server address and shared secret match Wiacom values. Confirm the controller can reach the RADIUS server on UDP 1812 and 1813.
FlexConnect mode only supports IP-based ACLs. Contact Wiacom for the current IP list for your region.
# Cisco WLC
Source: https://docs.wiacom.ai/wifi-vendors/cisco-wlc/overview
Wiacom Portal integration with Cisco Wireless LAN Controller (WLC)
Wiacom integrates with Cisco Wireless LAN Controllers (WLC) running firmware 7.6 or above using external splash page / Web Policy with RADIUS authentication.
This guide covers the **Cisco WLC** (standalone wireless controller). For Cisco Meraki cloud-managed networks, see the [Cisco Meraki](/wifi-vendors/cisco-meraki/overview) section.
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — |
## Requirements
* Cisco WLC, firmware 7.6 or above (tested on 8.3.150.0)
* Controller reachable on TCP/80, TCP/443, UDP/1812, UDP/1813
* Base Radio MAC address of each access point (forward to Wiacom before setup)
* RADIUS details and portal URL from Wiacom for your region
Step-by-step WLC configuration
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/draytek/onboarding
Configure Draytek Vigor for Wiacom Portal — legacy mode
Portal URL and RADIUS details are region-specific. Obtain them from Wiacom before starting.
## Step 1 — Add the Device to Wiacom
1. Go to **Inventory → Routers → Add New Router**
2. Select **Draytek / Vigor** from the vendor dropdown
3. Under **Network address**, enter the router's WAN MAC address (`AA:BB:CC:DD:EE:FF` format)
4. Leave NASID empty
5. Assign a location and click **Save**
## Step 2 — Create a Hotspot Profile
Log in to the Draytek router and go to **Hotspot Web Portal → Profile Setup**. Click an available index to edit.
### Login Method (Step 1)
Set login method to **RADIUS Login**.
### Whitelist / Walled Garden (Step 4)
Add the following domains:
| Category | Domains |
| -------------------- | ------------------------------------------------------------------------- |
| **Required** | `*.wiacom.ai` |
| Facebook / Instagram | `*.facebook.com`, `*.fbcdn.net`, `*.akamaihd.net`, `connect.facebook.net` |
| Google | `*.google.com`, `*.googleapis.com`, `*.gstatic.com` |
| Twitter / X | `*.twitter.com`, `*.twimg.com` |
| LinkedIn | `*.linkedin.com`, `*.licdn.net`, `*.licdn.com` |
Add any additional domains used in your portal customization.
### RADIUS Settings
| Field | Value |
| ------------------- | ------------------------ |
| RADIUS server | `` |
| Authentication port | `1812` |
| Accounting port | `1813` |
| Shared secret | `` |
### More Options (Step 5)
After **Save & Next**, go to **More Options**:
| Field | Value |
| --------------------------------- | -------------------------- |
| Landing Page After Authentication | `?res=success` |
| Captive Portal Detection | Enable |
## Step 3 — Apply to Guest Interface
Under **Applied Interfaces**, assign the profile to your guest WLAN interface(s) on both 2.4 GHz and 5 GHz radios as needed. Click **Finish**.
## Troubleshooting
Confirm the profile is applied to the correct WLAN interface and Captive Portal Detection is enabled. Disable HTTPS Redirection if guests browse HTTPS-only.
Verify RADIUS server address and shared secret match values from Wiacom.
# Overview
Source: https://docs.wiacom.ai/wifi-vendors/draytek/overview
Wiacom Portal integration with Draytek Vigor routers and APs
Wiacom integrates with Draytek Vigor routers and access points using the built-in **Hotspot Web Portal** with RADIUS authentication.
## Integration Mode
Draytek Vigor is onboarded in **legacy / manual mode** only.
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — |
## Requirements
* Draytek Vigor router or AP with admin access
* RADIUS server details and portal URL from Wiacom for your region
* A Wiacom account with a location created
Step-by-step Hotspot Web Portal configuration
# Overview
Source: https://docs.wiacom.ai/wifi-vendors/engenius/overview
Wiacom Portal integration with EnGenius Cloud-managed APs
Wiacom integration with EnGenius Cloud-managed access points is under vendor review. Portal and Key Access are planned. WiFi Pass availability depends on the EnGenius Cloud API capabilities and subscription tier.
## Supported Access Features
| Feature | Supported |
| ---------- | ------------------- |
| Portal | ✅ Planned |
| Key Access | Depends on platform |
| WiFi Pass | Vendor-dependent |
## Integration Mode
EnGenius Cloud supports a **Cloud API** integration path where available. The specific capabilities depend on firmware version and subscription tier.
## Current Status
Integration is under active vendor review. Contact [info@wiacom.ai](mailto:info@wiacom.ai) for current availability or to request prioritisation for your deployment.
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/fortinet/onboarding
Configure Fortinet FortiAP for Wiacom Portal
RADIUS details and portal URL are region-specific — obtain from Wiacom before starting.
## Step 1 — Add the Device to Wiacom
1. **Inventory → Routers → Add New Router**
2. Select **Fortinet / FortiAP**, fill in details, assign a location, click **Save**
Log in to your FortiCloud Dashboard (FortiLAN).
## RADIUS Servers
**Configure → My RADIUS Server → Add RADIUS Server** (twice — auth and accounting):
Auth server:
* Name: `guest_radius_server`, Primary IP: ``, Secret: ``, Port: `1812`, Secondary: ``
Accounting server:
* Name: `guest_radius_server_acct`, same IPs, Port: `1813`
## SSID
**SSIDs → Add SSID**:
| Field | Value |
| --------------------------- | -------------------------- |
| SSID | Your guest WiFi name |
| Authentication | Open |
| Captive Portal | My Captive Portal |
| Captive Portal URL | `` |
| Redirect URL | `?res=success` |
| Sign on Method | `guest_radius_server` |
| RADIUS Acct Settings | `guest_radius_server_acct` |
| Accounting Interim Interval | `120` |
Walled Garden — add domains:
```
*.wiacom.ai
*.akamaitechnologies.com
*.akamaiedge.net
*.akamaized.net
*.akamai.net
*.amazonaws.com
*.fastly.net
*.facebook.com
*.fbcdn.net
*.akamaihd.net
connect.facebook.net
*.instagram.com
*.twitter.com
*.twimg.com
*.linkedin.com
*.licdn.net
*.licdn.com
*.google.com
*.googleapis.com
*.gstatic.com
```
Click **Next → Next → Next → Save**.
Log in to your FortiGate web interface.
## RADIUS
**User & Authentication → RADIUS Servers → Create New**:
* Primary: ``, Secret: ``
* Secondary: ``
## Captive Portal
**Network → Interfaces → \[guest interface]**:
* Security Mode: Captive Portal, Authentication Portal: External
* External Auth Portal URL: ``
* RADIUS server: your Wiacom RADIUS profile
## Walled Garden
Create firewall address objects for the domains above and a policy allowing pre-auth access.
FortiGate walled garden configuration varies by FortiOS version. Contact the Wiacom team for assistance.
# Overview
Source: https://docs.wiacom.ai/wifi-vendors/fortinet/overview
Wiacom Portal integration with Fortinet FortiAP — FortiGate and FortiCloud
Wiacom integrates with Fortinet FortiAP access points managed through FortiGate or FortiCloud (FortiLAN).
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — |
## Management Variants
| Variant | Description |
| ------------------------- | ------------------------------------------ |
| **FortiGate** | FortiAPs managed locally through FortiGate |
| **FortiCloud (FortiLAN)** | FortiAPs managed via FortiCloud dashboard |
Step-by-step configuration for FortiGate and FortiCloud
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/huawei/onboarding
Configure Huawei WLAN Controller for Wiacom Portal — legacy mode
Firmware **V2R7C20 or above** is required. RADIUS server addresses and portal URLs are region-specific — obtain them from Wiacom before starting.
## Step 1 — Add the Device to Wiacom
1. Go to **Inventory → Routers → Add New Router**
2. Select **Huawei / WLAN Controller** from the vendor dropdown
3. Enter the required details and assign a location
4. Click **Save**
## Step 2 — Create a Guest VLAN
Log in to the Huawei WLAN Controller web interface → **Configuration**:
1. **AC Config → VLAN → Add**: set a VLAN ID (e.g. `500`), enable **Create VLANIF**
* Description: `guestwifi`, IP Address format: IPv4
* IPv4 Address/Mask: gateway IP for the guest subnet
2. **IP → DHCP**: ensure DHCP is enabled, click **Create**
* Address pool type: Interface address pool, Select interface: `VLAN`
* Advanced → Primary/Secondary DNS: your preferred DNS servers
## Step 3 — Configure Walled Garden (Domain ACL)
Go to **Security → ACL → Domain Name Configuration**. Add each domain with an incrementing Domain Name ID:
| Category | Domains |
| -------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Wiacom portal | `*.wiacom.ai` |
| Video / CDN | `fast.wistia.com`, `*.fastly.net`, `*.player.vimeo.com`, `*.akamaiedge.net`, `*.akamaized.net`, `*.amazonaws.com`, `*.zencdn.net` |
| Facebook / Instagram | `*.facebook.com`, `*.fbcdn.net`, `*.akamaihd.net`, `connect.facebook.net` |
| Twitter / X | `*.twitter.com`, `*.twimg.com` |
| LinkedIn | `*.linkedin.com`, `*.licdn.net`, `*.licdn.com` |
Under **User ACL Settings → Create**:
* ACL name: `guestwifi`, ACL number: `6030`
* For each domain: **Add Rule** → Action: Permit, Protocol: IP, Dest domain: select domain
## Step 4 — Configure External Portal Server
**Security → AAA → External Portal Server tab:**
* HTTP protocol: Enabled, HTTP interoperation mode: HTTP-based
* Port for listening to HTTP packets: `8000`
**Portal Authentication Server List → Create:**
| Field | Value |
| ----------- | ----------------------------------- |
| Server name | `guestwifi` |
| Server IP | Controller gateway IP (VLANIF) |
| URL | `` — provided by Wiacom |
**URL Option Settings:**
| Parameter | Value |
| ------------------- | --------------------------------------------- |
| AC-IP | `ac_ip` |
| User access URL | `redirect_url` |
| User IP | `user_ip` |
| SSID | `ssid` |
| Login URL / keyword | `login` / `http://:8000/login` |
| User MAC | `user_mac` |
| AP-MAC | `ap_mac` |
| MAC address format | `normal` |
| Separator | `:` |
**Parameter Parsing Configuration:**
* Protocol type: HTTP
* Login success response: Redirect to `?res=success`
## Step 5 — Configure RADIUS
**Security → AAA → RADIUS → RADIUS Server Profile → Create:**
* Profile name: `guestwifi`
* Key / Confirm key: ``
**Authentication/Accounting Server — Create twice:**
| | Auth Server | Accounting Server |
| ----------------- | -------------------- | -------------------- |
| Server type | Authentication | Accounting |
| IP address (IPv4) | `` | `` |
| Port | `1812` | `1813` |
| Weight | `1` | `1` |
## Step 6 — Configure Authentication Profile
1. **Authentication Profile → Create** → name `guestwifi`
2. Expand profile → **Portal Profile → Add** → name `guestwifi`
* Portal authentication: External portal server, Active server: `guestwifi`, Authentication mode: Layer 3
3. **RADIUS Server Profile** → select `guestwifi`
4. **Authentication Scheme → Add** → name `guestwifi`, First authentication: RADIUS
5. **Accounting Scheme → Add** → name `guestwifi`, Real-time accounting: On, Interval: `3`
6. **Authentication-free Rule Profile → Add** → name `guestwifi`, Control mode: ACL, ACL number: `6030`
7. **Advanced tab**: HTTPS Redirection Status: Off, Portal URL encoding: Off
## Step 7 — Configure VAP and SSID Profiles
1. **AP Config → Profile → VAP Profile → Create** → name `guestwifi`
* Status: On, VAP type: Service VAP, Forwarding mode: Tunnel
* Service VLAN ID: your guest VLAN, Home agent: AP, Layer 3 roaming: On, IP learning: On
2. **SSID Profile → Create** → name `guestwifi`, SSID: your guest WiFi name
3. **AP Group → \[group] → VAP Configuration → Add** → VAP profile: `guestwifi`, WLAN ID: available ID
4. Under `guestwifi` profile: SSID Profile → `guestwifi`
5. **Security Profile → Create** → name `guestwifi`, Security Policy: Open
6. **Authentication Profile** → select `guestwifi`
7. Click **Save** at the top to persist all settings
## Troubleshooting
Confirm HTTPS Redirection is Off and Portal URL encoding is Off in the Advanced tab.
Verify the RADIUS IP and shared secret match values provided by Wiacom. Confirm UDP 1812 and 1813 are reachable from the controller.
The Login URL uses the controller's own IP and port 8000 — not the Wiacom cloud URL.
# Overview
Source: https://docs.wiacom.ai/wifi-vendors/huawei/overview
Wiacom Portal integration with Huawei WLAN Controller
Wiacom integrates with Huawei WLAN Controllers (AC) and their managed access points using external portal authentication with RADIUS.
## Integration Mode
Huawei AC/AP is onboarded in **legacy / manual mode** only.
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — |
## Requirements
* Huawei WLAN Controller, firmware **V2R7C20 or above**
* RADIUS server details and portal URL provided by Wiacom for your region
* A Wiacom account with a location created
Step-by-step configuration for Huawei WLAN Controller
# Overview
Source: https://docs.wiacom.ai/wifi-vendors/index
Connecting Wiacom to your wireless infrastructure — supported vendors, integration modes, and compatibility.
Wiacom integrates with virtually any enterprise or SMB wireless infrastructure. The platform supports three integration modes — cloud API, local controller API, and manual configuration — and where neither API path is available, [Wiacom Agent](/integrations/wiacom-agent) can bridge the gap.
No hardware replacement is required. Wiacom works alongside your existing access points and controllers.
## Integration Modes
| Mode | How it works | When to use |
| ---------------------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| **Cloud API** | Wiacom connects directly to the vendor's cloud management platform | Vendor offers a cloud dashboard with an API (e.g. Cisco Meraki, Aruba Central) |
| **Local controller API** | Wiacom communicates with an on-premises controller | Vendor controller is self-hosted and exposes a local API (e.g. Ruckus SmartZone, UniFi) |
| **Manual / Legacy** | Device is configured directly with Wiacom RADIUS and portal settings | Any vendor — no API required |
| **[Wiacom Agent](/integrations/wiacom-agent)** | Local appliance bridges Wiacom cloud to equipment inside a private network | Equipment is only reachable locally — no cloud API available |
## Feature Compatibility
| Vendor / Platform | Portal | WiFi Pass | Key Access | API / Provisioning Mode |
| --------------------------------------------------------------- | :----: | :---------------: | :--------: | -------------------------- |
| [Cisco Meraki](/wifi-vendors/cisco-meraki/overview) | ✅ | ✅ | ✅ | Native Cloud API |
| [Cisco WLC](/wifi-vendors/cisco-wlc/overview) | ✅ | — | ✅ | Local Config |
| [HPE Aruba Instant / AOS 8](/wifi-vendors/aruba/overview) | ✅ | Possible | ✅ | Local API / Controller API |
| [HPE Aruba Central / AOS 10](/wifi-vendors/aruba/overview) | ✅ | Licence-dependent | ✅ | Native Cloud API |
| [Ruckus SmartZone / vSZ](/wifi-vendors/ruckus/overview) | ✅ | ✅ | ✅ | Local Config / NBI |
| [UniFi](/wifi-vendors/unifi/overview) | ✅ | Limited | ✅ | Controller API |
| [Cambium cnMaestro / XV](/wifi-vendors/cambium/overview) | ✅ | Vendor-dependent | ✅ | Controller API |
| [Fortinet FortiGate / FortiAP](/wifi-vendors/fortinet/overview) | ✅ | Limited | ✅ | Local Config |
| [MikroTik RouterOS](/wifi-vendors/mikrotik/overview) | ✅ | Limited | ✅ | Router API / Agent |
| [Xirrus / Cambium ArrayOS](/wifi-vendors/xirrus/overview) | ✅ | — | ✅ | Local / Agent |
| [Nomadix](/wifi-vendors/nomadix/overview) | ✅ | — | Limited | Local |
| [OpenWRT / CoovaChilli](/wifi-vendors/openwrt/overview) | ✅ | — | ✅ | Agent / Local Config |
| [TP-Link Omada](/wifi-vendors/tplink/overview) | ✅ | — | ✅ | Local Config |
| [Teltonika](/wifi-vendors/teltonika/overview) | ✅ | Limited | ✅ | Local Config |
| [Huawei WLAN AC](/wifi-vendors/huawei/overview) | ✅ | Vendor-dependent | ✅ | Local Config |
| [EnGenius Cloud](/wifi-vendors/engenius/overview) | ✅ | Vendor-dependent | Depends | Local Config |
| [Draytek Vigor](/wifi-vendors/draytek/overview) | ✅ | — | ✅ | Local Config |
Don't see your vendor? Most hardware with SSH/CLI access or a local management interface can be integrated via [Wiacom Agent](/integrations/wiacom-agent). Contact the Wiacom team to confirm compatibility.
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/mikrotik/onboarding
Configure MikroTik RouterBoard for Wiacom Portal — legacy mode
MikroTik is configured in legacy / manual mode using Winbox.
RADIUS server addresses, portal URLs, and shared secrets are region-specific. Obtain the correct values for your deployment from the Wiacom admin panel or the Wiacom team before starting.
## Step 1 — Add the Device to Wiacom
1. Go to **Inventory → Routers → Add New Router**
2. Select **MikroTik / RouterBoard** from the vendor dropdown
3. Under **Network address**, enter the WAN MAC address in `AA:BB:CC:DD:EE:FF` format
4. Leave NASID empty
5. Assign a location and click **Save**
## Step 2 — Configure RADIUS
Open Winbox, click **Radius** on the left menu, then **+**:
| Field | Value |
| ------------------- | ------------------------ |
| Service | `hotspot` |
| Address | `` |
| Secret | `` |
| Authentication Port | `1812` |
| Accounting Port | `1813` |
Click **OK**.
## Step 3 — Configure the Hotspot
Go to **IP → Hotspot → Hotspot Setup**:
| Field | Value |
| ------------------------ | --------------------------------------------------------------- |
| Hotspot Interface | WLAN interface, bridge, or ethernet port guests connect through |
| Local Address of Network | Guest subnet (e.g. `192.168.50.0/24`) |
| Masquerade Network | Yes |
| Address Pool | e.g. `192.168.50.2–192.168.50.254` |
| Select Certificate | None |
| DNS Servers | Your preferred DNS servers |
| DNS Name | Leave blank |
Click **OK**.
In the **Hotspot → Server** tab, double-click the new hotspot. **Rename it to the WAN MAC address** in `XX-XX-XX-XX-XX-XX` format (capitals, dashes). Find the WAN MAC at **Interfaces → ether1-gateway** (or your WAN interface).
## Step 4 — Configure the Server Profile
In **Server Profiles**, double-click the new profile:
**General tab:**
| Field | Value |
| --------------- | ------------------------------------------------ |
| Hotspot Address | Gateway IP of guest subnet (e.g. `192.168.50.1`) |
**Login tab:**
| Field | Value |
| ----------------- | -------- |
| HTTP PAP | Ticked |
| All other methods | Unticked |
**RADIUS tab:**
| Field | Value |
| -------------- | ------------------- |
| Use RADIUS | Ticked |
| MAC Format | `XX-XX-XX-XX-XX-XX` |
| Accounting | Ticked |
| Interim Update | `00:02:00` |
Click **OK**.
## Step 5 — Configure User Profiles
In **Hotspot → User Profiles**, double-click the **default** entry:
| Field | Value |
| ----------------- | -------------------- |
| Session Timeout | `24:00:00` |
| Idle Timeout | `00:30:00` |
| Keepalive Timeout | *(clear this field)* |
## Step 6 — Upload Portal Files
Wiacom provides two HTML files (`login.html` and `alogin.html`) for the MikroTik hotspot:
1. In Winbox go to **Files**
2. Locate the `hotspot` directory (under **HTML Directory** in the Hotspot Server Profile)
3. Drag and drop `login.html` and `alogin.html` into this directory
Contact the Wiacom team to receive the correct portal files for your region.
## Step 7 — Configure the Walled Garden
Open a **New Terminal** in Winbox and paste:
```
/ip hotspot walled-garden
add dst-host=*.wiacom.ai
add dst-host=*.facebook.com
add dst-host=*.fbcdn.net
add dst-host=connect.facebook.net
add dst-host=*.akamaihd.net
add dst-host=*.instagram.com
add dst-host=*.google.com
add dst-host=*.gstatic.com
add dst-host=*.googleapis.com
add dst-host=*.twitter.com
add dst-host=*.twimg.com
add dst-host=*.linkedin.com
add dst-host=*.licdn.net
add dst-host=fast.wistia.com
add dst-host=*.fastly.net
add dst-host=*.akamaized.net
add dst-host=*.amazonaws.com
add dst-host=*.zencdn.net
add dst-host=*.vimeocdn.com
```
Add any additional domains used in your portal customization.
## Optional — Automated Walled Garden Script
To keep the walled garden updated automatically, open a **New Terminal** and paste:
```
/system scheduler
add interval=1m name=checkSettingsCron on-event=checkSettings \
policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive \
start-time=startup
/system script
Ask Wiacom of partner for content
```
## Troubleshooting
Confirm the hotspot server name matches the WAN MAC in `XX-XX-XX-XX-XX-XX` format. Confirm HTTP PAP is the only enabled login method.
Verify the RADIUS server address and shared secret match values provided by Wiacom for your region. Check UDP 1812 and 1813 are reachable.
# Overview
Source: https://docs.wiacom.ai/wifi-vendors/mikrotik/overview
Wiacom Portal integration with MikroTik RouterBoard
Wiacom integrates with MikroTik RouterBoard devices using the built-in **Hotspot** feature with external RADIUS authentication, providing captive portal (Portal) and Key Access functionality.
## Integration Mode
MikroTik devices are onboarded in **legacy / manual mode** only. There is no cloud API integration for MikroTik.
## Supported Access Features
| Feature | Supported |
| ---------- | ----------------------------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — (not available without API) |
## Requirements
* MikroTik RouterBoard with Winbox access
* Latest stable firmware (update via *System → Packages → Check for Updates*)
* RADIUS server details and portal URL provided by Wiacom for your region
* A Wiacom account with a location created
Step-by-step configuration for MikroTik RouterBoard
# Nomadix
Source: https://docs.wiacom.ai/wifi-vendors/nomadix/overview
Wiacom Portal integration with Nomadix gateways
Wiacom integrates with Nomadix gateways using the Nomadix Gateway API and RADIUS. Portal is fully supported. Key Access availability depends on the model and configuration. WiFi Pass (iPSK) is not natively available on this platform.
## Supported Access Features
| Feature | Supported |
| ---------- | ------------------------- |
| Portal | ✅ |
| Key Access | Limited — model-dependent |
| WiFi Pass | — |
## Integration Mode
Nomadix uses a **Gateway API / RADIUS** integration mode. Wiacom communicates with the gateway over RADIUS for per-user session authentication and uses the Nomadix API for device and session management where supported.
## Requirements
* Nomadix gateway with API access enabled
* RADIUS server details and portal URL from Wiacom for your region
* A Wiacom account with a location created
Contact [info@wiacom.ai](mailto:info@wiacom.ai) for assisted onboarding of Nomadix equipment.
# OpenWRT / CoovaChilli
Source: https://docs.wiacom.ai/wifi-vendors/openwrt/overview
Wiacom Portal integration with OpenWRT and CoovaChilli
Wiacom supports OpenWRT-based routers and CoovaChilli captive portal deployments via local agent or direct configuration. Portal and Key Access are supported. WiFi Pass (iPSK) is not available natively on this platform.
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — |
## Integration Mode
OpenWRT / CoovaChilli is integrated via **Agent / Local Config** — Wiacom's lightweight provisioning component installs on the device and manages RADIUS configuration and portal redirection locally. This provides full Portal functionality on commodity hardware without a vendor cloud API.
This is a common deployment path for custom-built or white-label gateway hardware running OpenWRT or derivative firmware.
Horizon personal WiFi provisioning is supported through the Wiacom agent where CLI access is available. See [Horizon](/access-features/horizon/overview) for details.
## Requirements
* OpenWRT or CoovaChilli-based device with SSH / admin access
* RADIUS server details and portal URL from Wiacom for your region
* A Wiacom account with a location created
Contact [info@wiacom.ai](mailto:info@wiacom.ai) for assisted onboarding of OpenWRT / CoovaChilli deployments.
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/ruckus/onboarding
Configure Ruckus for Wiacom Portal — all variants
RADIUS server details and portal URL are region-specific. Obtain the correct values from Wiacom before starting.
## Step 1 — Add the Device to Wiacom
1. Go to **Inventory → Routers → Add New Router**
2. Select **Ruckus** from the vendor dropdown
3. Enter the required details and assign a location
4. Click **Save**
Log in to your SmartZone web interface.
## AAA Servers
**Services & Profiles → Authentication** → Proxy (SZ Authenticator) tab → **Create**:
| Field | Value |
| ----------------------- | ------------------------ |
| Name | `Guest WiFi` |
| Service Protocol | RADIUS |
| Primary Server IP | `` |
| Port | `1812` |
| Shared Secret | `` |
| Secondary Server IP | `` |
| Secondary Port | `1812` |
| Secondary Shared Secret | `` |
**Accounting** → Proxy tab → **Create**:
| Field | Value |
| ------------------- | ------------------------ |
| Name | `Guest WiFi Acct` |
| Primary Server IP | `` |
| Port | `1813` |
| Shared Secret | `` |
| Secondary Server IP | `` |
| Secondary Port | `1813` |
## Hotspot (WISPr)
**Hotspots & Portals** → Hotspot (WISPr) tab → **Create**:
| Field | Value |
| --------------------------------- | --------------------------------------- |
| Portal Name | `Guest Wi-Fi` |
| Smart Client Support | None |
| Login URL | External |
| Redirect unauthenticated users to | `` |
| Redirected MAC Format | `AA-BB-CC-DD-EE-FF` |
| HTTPS Redirect | ON |
| Start Page | Redirect to: `?res=success` |
## Walled Garden
Add the following domains one by one:
```
*.wiacom.ai
*.akamaitechnologies.com
*.akamaiedge.net
*.akamaized.net
*.akamai.net
*.amazonaws.com
*.fastly.net
*.zencdn.net
fast.wistia.com
player.vimeo.com
*.facebook.com
*.fbcdn.net
*.akamaihd.net
connect.facebook.net
*.instagram.com
*.twitter.com
*.twimg.com
*.linkedin.com
*.licdn.net
*.licdn.com
```
## Wireless LAN
**Wireless LANs** → **Create**:
* Name / SSID: your guest WiFi name
* Zone / WLAN Group: select as appropriate
* Authentication Type: **Hotspot (WISPr)**
* Method: **Open**
* Encryption Method: **None**
* Hotspot Portal: select `Guest Wi-Fi`
* Authentication Service: `Guest WiFi`
* Accounting Service: `Guest WiFi Acct`
* NAS ID: **AP MAC**
* Called STA ID: **AP MAC**
Log in to your Ruckus ZoneDirector web interface.
## AAA Servers
**Configure → AAA Servers** → **Create New**:
Auth server:
* Name: `Guest WiFi`, Type: RADIUS, Auth Method: PAP
* Primary IP: ``, Port: `1812`, Secret: ``
* Secondary IP: ``, Port: `1812`
Accounting server:
* Name: `Guest WiFi Acct`, Type: RADIUS Accounting
* Primary IP: ``, Port: `1813`
* Secondary IP: ``, Port: `1813`
## Hotspot (WISPr)
**Configure → Hotspot WISPr** → **Create New**:
| Field | Value |
| --------------------- | --------------------------------------- |
| Login URL | External: `` |
| Start Page | Redirect to: `?res=success` |
| Redirected MAC Format | `AA-BB-CC-DD-EE-FF` |
Add walled garden domains from the list above.
## WLAN
**Configure → WLANs** → **Create New**:
* Name / SSID: your guest WiFi name
* Type: **Hotspot (WISPr)**
* Authentication Server: `Guest WiFi`
* Accounting Server: `Guest WiFi Acct`
* Hotspot Profile: select the profile you created
Log in to your ZoneDirector web interface.
## AAA Servers
**Configure → AAA Servers** → **Create New**:
* Name: `Guest WiFi`, Type: RADIUS, Auth Method: PAP
* Primary IP: ``, Port: `1812`, Secret: ``
* Secondary IP: ``
Repeat for accounting (port `1813`).
## Hotspot (WISPr)
**Configure → Hotspot WISPr** → **Create New**:
* Login URL: ``
* Start Page: Redirect to `?res=success`
* Redirected MAC Format: `AA-BB-CC-DD-EE-FF`
Add walled garden domains from the list above.
## WLAN
Create a WLAN, set Type to **Hotspot (WISPr)**, open authentication, assign the Hotspot profile, auth, and accounting servers.
Log in to [cloud.ruckuswireless.com](https://cloud.ruckuswireless.com).
## Create a Network
**Networks → Add Network**:
* Network Name: your guest WiFi name
* Type: **Captive Portal**
Click **Next**:
* Captive Portal Type: **3rd Party Captive Portal (WISPr)**
Click **Next**:
* Portal URL: `` — provided by Wiacom
* Note the **Integration Key** — enter it in the Wiacom admin under the venue settings
## Walled Garden
Add domains from the list above.
Click **Next**, select which Venue to apply to, enable it, and complete.
Ensure you copy the Integration Key to the Wiacom admin under Venue → Settings to enable the connection.
## Troubleshooting
Confirm the WLAN is set to Hotspot (WISPr) type and Authentication is Open. The NAS ID should be None for SmartZone general procedure.
Verify RADIUS server addresses and shared secret. UDP 1812 and 1813 must be reachable from the controller.
# Overview
Source: https://docs.wiacom.ai/wifi-vendors/ruckus/overview
Wiacom Portal integration with Ruckus wireless — SmartZone, ZoneDirector, and Cloud AP
Wiacom integrates with Ruckus wireless infrastructure across four management platforms. All support Portal access via Hotspot (WISPr) with RADIUS authentication.
## Supported Access Features
| Feature | Supported |
| ---------- | ------------------------------ |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | ✅ (SmartZone and ZoneDirector) |
## Hardware / Management Variants
| Variant | Description |
| --------------------------------- | ------------------------------------------------------ |
| **SmartZone (v3.0+)** | Centralised SmartZone controller — physical or virtual |
| **ZoneDirector (v9.8+)** | Standalone ZoneDirector controller |
| **ZoneDirector (v9.7 and below)** | Legacy ZoneDirector — older configuration flow |
| **Ruckus Cloud AP** | Cloud-managed APs via cloud.ruckuswireless.com |
Step-by-step configuration for all Ruckus variants
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/teltonika/onboarding
Configure Teltonika RUTX for Wiacom Portal — legacy mode
Portal URL, UAM secret, and RADIUS details are region-specific. Obtain them from Wiacom before starting.
## Step 1 — Create Guest WiFi SSIDs
1. Log in to the router web interface
2. Go to **Network → Wireless**
3. Add a new WiFi SSID (e.g. *Wiacom FreeWifi*) without a network assignment
4. Repeat for the second radio if available — use the same SSID name on both
5. **Save & Apply**
Note the **BSSID** of each new WLAN interface and send them to the Wiacom team — they are required as the NAS-ID value for RADIUS. The BSSID is visible in the wireless interface list after saving.
## Step 2 — Add the Device to Wiacom
1. Go to **Inventory → Routers → Add New Router**
2. Select **Teltonika / RUTX** from the vendor dropdown
3. Enter the primary WLAN BSSID as the NAS-ID
4. Assign a location and click **Save**
## Step 3 — Configure the Hotspot
Go to **Services → Hotspot → General**, create a new hotspot on one of the new WLAN interfaces.
**General Settings:**
| Field | Value |
| -------------------- | -------------- |
| Enabled | On |
| Authentication mode | RADIUS |
| Landing page | External |
| Password encoding | On |
| Landing page address | `` |
| UAM Port | `3990` |
| UAM secret | `` |
| Success page | Success page |
**Advanced Settings:**
* Additional interfaces: add the second WLAN interface if present
## Step 4 — Configure RADIUS
| Field | Value |
| ------------------- | ---------------------------------------------------------------- |
| RADIUS server #1 | `` |
| RADIUS server #2 | `` |
| Authentication port | `1812` |
| Accounting port | `1813` |
| NAS identifier | BSSID of primary WLAN in hyphenated format (`XX-XX-XX-XX-XX-XX`) |
| RADIUS secret key | `` |
NAS identifier must use **hyphens** (`-`), not colons (`:`). Send this value to Wiacom.
## Step 5 — Configure the Walled Garden
Under the **Walled Garden** section:
| Category | Domains |
| -------------------- | ------------------------------------------------------------------------------------------------- |
| **Required** | `wiacom.ai` |
| Facebook / Instagram | `facebook.com`, `fbcdn.net`, `akamaihd.net`, `connect.facebook.net` |
| Google | `google.com`, `googleapis.com`, `gstatic.com` |
| Twitter / X | `twitter.com`, `twimg.com` |
| LinkedIn | `linkedin.com`, `licdn.net`, `licdn.com` |
| Video / CDN | `fast.wistia.com`, `fastly.net`, `akamaiedge.net`, `akamaized.net`, `amazonaws.com`, `zencdn.net` |
**Save & Apply**.
## Troubleshooting
Verify the NAS identifier matches the WLAN BSSID exactly, using hyphens. Confirm Authentication mode is RADIUS and Landing page is External.
Verify RADIUS server addresses and shared secret. Confirm UDP 1812 and 1813 are reachable.
# Teltonika RUTX
Source: https://docs.wiacom.ai/wifi-vendors/teltonika/overview
Wiacom Portal integration with Teltonika RUTX series routers
Wiacom integrates with Teltonika RUTX-series routers using the built-in **Hotspot** feature with external portal and RADIUS authentication.
## Integration Mode
Teltonika RUTX is onboarded in **legacy / manual mode** only.
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — |
## Requirements
* Teltonika RUTX router with web interface access
* RADIUS server details, portal URL, and UAM secret from Wiacom for your region
* A Wiacom account with a location created
Step-by-step Hotspot configuration for Teltonika RUTX
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/tplink/onboarding
Configure TP-Link Omada EAP for Wiacom Portal
RADIUS details and portal URL are region-specific — obtain from Wiacom before starting.
## Step 1 — Add the Device to Wiacom
1. **Inventory → Routers → Add New Router**
2. Select **TP-Link / Omada**, fill in details, assign a location, click **Save**
## Step 2 — Create the SSID
Log in to your Omada controller. **Wireless Settings → Add**:
| Field | Value |
| ------------- | -------------------- |
| SSID | Your guest WiFi name |
| Band | 2.4 GHz and 5 GHz |
| Guest Network | Enabled |
| Security Mode | None |
Click **Apply**.
## Step 3 — Configure the Guest Portal
**Wireless Control → Portal → Add a New Portal**:
| Field | Value |
| -------------------------- | --------------------------- |
| Portal Name | `guestwifi` |
| SSID | Select the SSID you created |
| Authentication Type | External RADIUS Server |
| Authentication Timeout | 8 Hour |
| RADIUS Server IP | `` |
| RADIUS Port | `1812` |
| RADIUS Password | `` |
| Authentication Mode | PAP |
| NAS ID | `guestwifi` |
| RADIUS Accounting | Enable |
| Accounting Server IP | `` |
| Accounting Server Port | `1813` |
| Accounting Server Password | `` |
| Interim Update | Enable, `120` |
| Portal Customization | External Web Portal |
| External Web Portal URL | `` |
| HTTPS Redirect | Disable |
| Landing Page | Promotional URL |
| Promotional URL | `?res=success` |
Click **Apply**.
## Step 4 — Configure Walled Garden
**Access Control → Pre-authentication Access → Enable**
Under Pre-Authentication Access List, add each domain:
```
*.wiacom.ai
*.akamaitechnologies.com
*.akamaiedge.net
*.akamaized.net
*.akamai.net
*.amazonaws.com
*.fastly.net
*.facebook.com
*.fbcdn.net
*.akamaihd.net
connect.facebook.net
*.instagram.com
*.twitter.com
*.twimg.com
*.linkedin.com
*.licdn.net
*.licdn.com
*.google.com
*.googleapis.com
*.gstatic.com
```
Click **Apply**.
## Troubleshooting
Confirm HTTPS Redirect is Disabled — only HTTP traffic triggers the redirect. Try `http://neverssl.com` for testing.
Verify server IP and password match Wiacom values. UDP 1812 and 1813 must be reachable.
# TP-Link Omada
Source: https://docs.wiacom.ai/wifi-vendors/tplink/overview
Wiacom Portal integration with TP-Link Omada EAP
Wiacom integrates with TP-Link Omada EAP access points via the Omada Controller (v4+). Portal access via external RADIUS is fully supported.
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — |
## Requirements
* Latest Omada Controller software (v4 or above)
* RADIUS details and portal URL from Wiacom for your region
Step-by-step configuration for TP-Link Omada EAP
# Onboarding
Source: https://docs.wiacom.ai/wifi-vendors/unifi/onboarding
Connect UniFi to Wiacom — API and legacy modes
## Prerequisites
* UniFi controller accessible from the internet (or Wiacom source IPs allowed through your firewall — contact Wiacom for the IP list)
* Open SSID(s) configured under Sites with Access Points assigned
* UniFi controller URL, admin username, and password
* Same controller not previously provisioned on the Wiacom platform
One Site profile from the UniFi controller can be assigned to only one Wiacom location. Long loading times may occur on controllers with many Sites and APs.
## UniFi Dashboard Preparation
For each SSID you want to use with Portal:
1. Select the desired **Site**
2. Set the SSID **Security** to **Open**
3. Enable **Guest Policy** on the SSID
4. The SSID can remain disabled initially
## Add the Controller in Wiacom
1. Go to **Inventory → Controllers → Add new Controller**
2. Choose **UniFi controller**
3. Fill in the controller URL, username, and password
4. Click **Next**
## Map Sites to Locations
1. Select the Sites (SSIDs) to integrate with Wiacom
2. You may choose **No location mapping** to leave a Site unassigned
3. Map each selected Site to a Wiacom venue location
4. Click **Finish**
Wiacom will discover APs and SSIDs and configure the splash redirect automatically.
RADIUS server details and portal URL are region-specific. Obtain the correct values from Wiacom before starting.
## Step 1 — Add the Device to Wiacom
1. Go to **Inventory → Routers → Add New Router**
2. Select **UniFi** from the vendor dropdown
3. Enter required details and assign a location
4. Click **Save**
## Step 2 — Configure the SSID in UniFi
Log in to your UniFi controller. Select the desired Site.
Create or edit the guest SSID:
* Security: **Open**
* Enable Guest Policy: **Yes**
Under the Guest Control settings for the SSID:
* Enable **Guest Portal**
* Portal type: **External Portal Server**
* Custom Portal URL: `` — provided by Wiacom
## Step 3 — Configure RADIUS
Under **Settings → Profiles → RADIUS**:
* Create an auth profile with your Wiacom RADIUS server IP and shared secret (port `1812`)
* Create an accounting profile (port `1813`)
Assign the RADIUS profiles to the SSID.
## Step 4 — Configure Pre-Authorization Access (Walled Garden)
Under **Guest Control → Pre-Authorization Access**, add:
```
*.wiacom.ai
*.akamaitechnologies.com
*.akamaiedge.net
*.akamaized.net
*.akamai.net
*.amazonaws.com
*.fastly.net
*.facebook.com
*.fbcdn.net
*.akamaihd.net
connect.facebook.net
*.instagram.com
*.twitter.com
*.twimg.com
*.linkedin.com
*.licdn.net
*.licdn.com
*.google.com
*.googleapis.com
*.gstatic.com
```
## Troubleshooting
Ensure the controller URL includes the port (e.g. `https://your-controller:8443`). If behind a firewall, allow Wiacom source IPs — contact the Wiacom team for the current IP list.
Confirm Guest Policy is enabled on the SSID and the SSID is set to Open. HTTPS pages will not trigger the redirect — use an HTTP URL for testing.
# UniFi
Source: https://docs.wiacom.ai/wifi-vendors/unifi/overview
Wiacom Portal integration with UniFi wireless — API and legacy modes
Wiacom integrates with UniFi wireless networks via the **UniFi Network API** for controller onboarding. Portal, Key Access, and WiFi Pass are all supported.
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | ✅ |
## Integration Modes
| Mode | Description |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| **API** | Wiacom connects to your UniFi controller over the network, discovers Sites and SSIDs, and maps them to locations automatically |
| **Legacy / manual** | SSID configured manually in the UniFi controller; device added to Wiacom inventory |
API and manual configuration steps
# Xirrus / Cambium ArrayOS
Source: https://docs.wiacom.ai/wifi-vendors/xirrus/overview
Wiacom Portal integration with Xirrus and Cambium ArrayOS arrays
Wiacom integrates with Xirrus arrays and Cambium ArrayOS-based equipment via SSH agent automation. Portal and Key Access are supported. WiFi Pass (iPSK) is not available on this platform.
## Supported Access Features
| Feature | Supported |
| ---------- | --------- |
| Portal | ✅ |
| Key Access | ✅ |
| WiFi Pass | — |
## Integration Mode
Xirrus / Cambium ArrayOS equipment is managed via **SSH Agent** — Wiacom's lightweight provisioning component that connects to the array over SSH and applies configuration changes directly, without requiring a vendor cloud API.
Horizon personal WiFi provisioning is also supported through the Wiacom agent where CLI access is available. See [Horizon](/access-features/horizon/overview) for details on personal SSID and WiFi teleport capabilities.
## Requirements
* SSH access to the array (management interface)
* RADIUS server details and portal URL from Wiacom for your region
* A Wiacom account with a location created
Contact [info@wiacom.ai](mailto:info@wiacom.ai) for assisted onboarding of Xirrus / Cambium ArrayOS equipment.