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

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

<Info>
  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.
</Info>

## Available Features

<CardGroup cols={2}>
  <Card title="Portal" icon="browser" href="/access-features/portal/overview">
    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.
  </Card>

  <Card title="WiFi Pass" icon="fingerprint" href="/access-features/wifi-pass/overview">
    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.
  </Card>

  <Card title="Key Access" icon="key" href="/access-features/key-access/overview">
    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.
  </Card>

  <Card title="Passpoint Connect" icon="signal" href="/access-features/passpoint-connect/overview">
    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.
  </Card>

  <Card title="Horizon" icon="sparkles" href="/access-features/horizon/overview">
    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.
  </Card>
</CardGroup>

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