Skip to main content
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 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:
For the full vendor compatibility table, see Supported WiFi Vendors.
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:
CategoryDomains
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.