Guest access as a separate digital service

Guest Wi‑Fi Authentication for Hotels

We design the guest journey from Wi‑Fi connection to internet access: a captive portal, an agreed identification method, session policies, logging, and integrations. Before including a function, we verify the external system version, available interface, and failure scenarios.

The guest Wi-Fi authentication journeyA diagram showing connection to Wi-Fi, portal access, user verification, policy enforcement and logging.

Wi‑Fi connection → captive portal → identity verification → access policy → internet and logs

Authentication is a separate layer above a working Wi‑Fi network

The authentication system manages user login, the portal, session policies, and data exchange with external systems. It does not correct weak coverage, excessive airtime utilization, or roaming errors. RF coverage, capacity, VLANs, and client isolation belong to the WLAN and must be designed or assessed separately.

Once the workflow is agreed, the platform can apply access profiles, communicate with guests through the login page, and pass authorized data to external systems. Internet link utilization monitoring helps operations teams understand resource consumption and check policy enforcement. Specific functions are included only after the platform, integrations, and legal bases have been validated.

Signs that a solution is needed

When existing authentication disrupts guests and operations

01

Guests cannot find a clear way to sign in

The portal is overloaded, does not work well on a mobile device or requires unnecessary action.

02

There is no single policy

Different unrelated scenarios are used in the rooms, lobby and events.

03

Integration is unstable

Room number, ticket or account are checked manually or with errors.

04

It is unclear what is being logged

There is no agreed composition of events, storage periods and responsibility of systems.

Solution scope

Functions, integrations and requirements are fixed before launch

01

State of Wi‑Fi

Captive portal does not compensate for weak coverage, RF environment overload or roaming breaks.

02

Source of identification

For each agreed source used to verify identity, we document the interface, available data, integration owner, rejection handling, and session restrictions. A method is included only after confirming its suitability for the selected platform and project.

03

Personal data

The composition of the fields, roles and storage periods are determined by the customer’s processes and legal requirements.

04

Client devices

Captive portal opens differently in mobile OS and browsers; the path is tested on target devices.

Architecture of service

Five levels of guest access

01

Connect to Wi‑Fi

The guest SSID, network segment, and client isolation belong to the WLAN. The authentication system uses this infrastructure but does not replace its design.

02

Captive portal

A responsive branded page with a clear user journey.

03

Validation

The agreed source of identification is activated only after confirmation of its applicability to the selected platform and project.

04

Access policy

Session duration, speed, available resources and re-entry rules.

05

Logging and integration

Authorization events, exchange with external systems and operational monitoring.

Methods of identification

Stages of the project

From guest path map to controlled launch

  1. 01

    Scenarios and roles

    Define zones, user categories, login methods and process owners.

  2. 02

    Verification of integrations

    Document API, available data, error handling and test environment.

  3. 03

    Prototype of the portal

    Develop the screens, copy, states, and brand design.

  4. 04

    Policy configuration

    Configure segments, session duration, limits, and repeat sign-in rules.

  5. 05

    Testing and launch

    Check devices, zones, identification methods and failure scenarios.

Results of the project

What is transferred to the customer

  • 01Map of user scenarios and portal states
  • 02A responsive branded captive portal
  • 03Configured identification methods and access policies
  • 04Description of confirmed integrations and boundaries of responsibility
  • 05Test protocol and operating instructions

Acceptance

We test the entire journey, including errors

CriterionHow to checkWhere we document
PortalOpen the portal and complete the login journey on agreed mobile operating systems and browsers.Device matrix and test results.
IdentificationPositive, negative and repeated attempts for each method.Scenario protocol and event log.
IntegrationExchange with test and production environment of the external system.List of verified requests and error handling.
PolicyCheck session duration, number of devices, speed and network isolation.Settings and results of control connections.

Safety and operation

How guest access is controlled

01

WLAN boundaries

The guest segment is separated from service systems and client devices from each other.

02

Minimization of data

Only the fields that are needed by the agreed scenario are collected.

03

Logging

Necessary login events and technical integration errors are recorded.

04

Access management

Administrative roles, backups and changes are configured according to the regulations.

05

Terms of the project

The schedule is defined after reviewing project inputs and, where necessary, surveying the site. Design, delivery, installation, commissioning, and acceptance are planned separately.

06

Cost

Cost depends on location, areas to be covered, the client device mix, cabling and backbone condition, equipment, work, and integrations. We document the estimate after defining the project scope.

07

SLA and Support

Response targets, support arrangements, monitoring, spare equipment, and restoration procedures are agreed separately according to the criticality of operations.

Questions and answers

Frequently asked questions about the solution

01Can a guest sign in using a room number?

Only when the selected platform and hotel system support an agreed data exchange. Before offering this function, we check the exact system name and version, interface, data fields, and test environment. Checkout, room changes, multiple guests, and unavailable integrations require separately agreed handling. Without verified compatibility, this method is not included.

02Which login methods can work without a PMS?

The method depends on the platform, available external systems, and the intended user journey. We also consider external service costs, data requirements, rejection handling, and legal review. Only methods verified for the selected configuration and project appear in the proposal and portal interface. Unverified options are not presented as available functions.

03What happens if an external system is unavailable?

Each integration has an agreed failure procedure and an owner responsible for the external system. Users receive a clear message, and operations teams receive the agreed diagnostic events. Retry, staff assistance, or a fallback login method is offered only where supported by the approved design. Automatic bypass of identification is not assumed when an external system is unavailable.

04Will authentication fix poor Wi‑Fi?

No. The portal handles login and agreed session policies; it does not change RF coverage, capacity, or client roaming behavior. These, together with network isolation, belong to the WLAN. If problems occur before the portal opens, during Wi‑Fi connection, or while moving, we first check the wireless and wired infrastructure and distinguish network faults from authentication errors.

05Does the platform guarantee compliance with the law?

No. A technical platform implements an agreed login, policy, and logging design but does not itself establish that the process is lawful. Identification methods, data, legal bases and retention periods, documents, party roles, and transfer procedures require separate legal review as of launch. If the design or regulations change, that review is updated before new claims are published.

06Which devices are used to test the captive portal?

The test matrix is agreed for the site’s actual audience. It includes selected operating system and browser versions, built-in captive portal windows, and first login, reconnection, and error states where applicable. Results apply to the device and software versions tested; support for every possible combination is not assumed.

07Is it possible to limit the number of devices and the duration of the session?

Limits can be enabled only where supported by the selected platform, WLAN, and agreed access control design. Before launch, we document session duration, repeat sign-in, device counts, access profiles, and behavior when moving between areas or sites. Each claimed policy is tested. Unverified settings are not published as available options.

08Is it possible to brand the portal and connect the loyalty program?

Branding is available where supported by the platform and included in the project. Before development, we agree on screens, copy, error states, and accessibility while retaining a clear login journey. Loyalty program integration is assessed separately and requires a verified interface, data owner, legal bases, test environment, and agreed workflow. Without these, it is not included.

The next step

We will design the guest access process

Describe the areas, identification methods, and external systems involved. Include available APIs, data fields, and error handling requirements. We will assess integration feasibility and propose a user journey.

Material prepared by Connectum technical team · updated: August 2026

Do not pass through the public form secrets, passwords and API working keys.

Integration with PMS