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

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

<Note>
  **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.
</Note>

## Why WiFi Pass?

<CardGroup cols={2}>
  <Card title="Individual credentials" icon="fingerprint">
    Every user gets their own passphrase — no sharing, no circulation
  </Card>

  <Card title="Instant revocation" icon="ban">
    Revoke a single user's access without affecting anyone else
  </Card>

  <Card title="Credential expiry" icon="clock">
    Passphrases expire after a configurable period and are renewed on re-registration
  </Card>

  <Card title="Per-user audit trail" icon="user-check">
    Every connection is tied to a known, consented registered user
  </Card>
</CardGroup>

## How It Works

<Steps>
  <Step title="User registers">User registers through any configured onboarding channel (Guest Connect, portal, API, PMS, App, online resource).</Step>
  <Step title="Credential provisioned">Wiacom creates a unique PSK on the WiFi AP/controller.</Step>
  <Step title="Network details delivered">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).</Step>
  <Step title="User connects">User connects using standard WPA2 — no app, no profile, no special client required.</Step>
  <Step title="Lifecycle managed">Access is revocable and expiry-controlled from the Wiacom dashboard at any time.</Step>
</Steps>

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

<Tip>
  Confirmed mode validates provided registration details before issuing a credential — recommended for public-facing deployments.
</Tip>

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

<CardGroup cols={2}>
  <Card title="Requirements" href="/access-features/wifi-pass/requirements">
    Hardware and firmware requirements by vendor
  </Card>

  <Card title="Enabling WiFi Pass" href="/access-features/wifi-pass/enabling">
    Activate and configure WiFi Pass on a location
  </Card>
</CardGroup>