> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wiacom.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# 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

<Steps>
  <Step title="Guest connects">Guest connects to the open WiFi SSID.</Step>
  <Step title="Redirect">The controller redirects the guest's HTTP traffic to the Wiacom portal URL.</Step>
  <Step title="Onboarding">Guest completes the registration form, accepts terms, or logs in via a social provider.</Step>
  <Step title="RADIUS authentication">Wiacom sends a RADIUS Access-Request with a generated per-session credential to the RADIUS server.</Step>
  <Step title="Access granted">RADIUS returns Access-Accept; the controller grants the guest internet access for the configured session duration.</Step>
</Steps>

## 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        |

<Note>
  For the full vendor compatibility table, see [Supported WiFi Vendors](/wifi-vendors/index).
</Note>

<Card title="Setting up Portal" href="/access-features/portal/setting-up">
  Configure Portal for your location — forms, appearance, and session settings
</Card>