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

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

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

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

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

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