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.
Guest access as a separate digital service
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.
Wi‑Fi connection → captive portal → identity verification → access policy → internet and logs
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
The portal is overloaded, does not work well on a mobile device or requires unnecessary action.
Different unrelated scenarios are used in the rooms, lobby and events.
Room number, ticket or account are checked manually or with errors.
There is no agreed composition of events, storage periods and responsibility of systems.
Solution scope
Captive portal does not compensate for weak coverage, RF environment overload or roaming breaks.
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.
The composition of the fields, roles and storage periods are determined by the customer’s processes and legal requirements.
Captive portal opens differently in mobile OS and browsers; the path is tested on target devices.
Architecture of service
The guest SSID, network segment, and client isolation belong to the WLAN. The authentication system uses this infrastructure but does not replace its design.
A responsive branded page with a clear user journey.
The agreed source of identification is activated only after confirmation of its applicability to the selected platform and project.
Session duration, speed, available resources and re-entry rules.
Authorization events, exchange with external systems and operational monitoring.
Legal framework
The platform implements agreed login methods, access policies, and logging. It does not by itself guarantee that a particular site meets all legal requirements. Before launch, the customer and their legal team determine the permissible identification method, data to be processed, legal bases and retention periods, access, deletion and transfer procedures, and the roles of the parties involved.
Connectum documents the technical architecture, processing and storage locations, logged events, administrator access, exchanges with external systems, and responsibilities. A qualified lawyer should verify legal requirements and regulatory references as of the project launch date.
Stages of the project
Define zones, user categories, login methods and process owners.
Document API, available data, error handling and test environment.
Develop the screens, copy, states, and brand design.
Configure segments, session duration, limits, and repeat sign-in rules.
Check devices, zones, identification methods and failure scenarios.
Results of the project
Acceptance
| Criterion | How to check | Where we document |
|---|---|---|
| Portal | Open the portal and complete the login journey on agreed mobile operating systems and browsers. | Device matrix and test results. |
| Identification | Positive, negative and repeated attempts for each method. | Scenario protocol and event log. |
| Integration | Exchange with test and production environment of the external system. | List of verified requests and error handling. |
| Policy | Check session duration, number of devices, speed and network isolation. | Settings and results of control connections. |
Safety and operation
The guest segment is separated from service systems and client devices from each other.
Only the fields that are needed by the agreed scenario are collected.
Necessary login events and technical integration errors are recorded.
Administrative roles, backups and changes are configured according to the regulations.
The schedule is defined after reviewing project inputs and, where necessary, surveying the site. Design, delivery, installation, commissioning, and acceptance are planned separately.
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.
Response targets, support arrangements, monitoring, spare equipment, and restoration procedures are agreed separately according to the criticality of operations.
Questions and answers
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.
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.
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.
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.
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.
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.
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.
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
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.