A Login Profile defines how users register, sign in, and gain access through the Cloud4Wi Splash Portal. It controls the available identification methods, data collected during registration, verification requirements, policy acceptance, and returning-user experience.
A Login Profile works together with a Splash Page: the Login Profile defines the onboarding and authentication rules, while the Splash Page defines the page's content and appearance. You associate them when configuring a Location or a Passpoint Onboarding Portal.
This article describes the settings in the three Login Profile tabs—Login options, Advanced, and Policies—and their effects. Some settings appear only for particular sign-up methods, enabled applications, or compatible configurations. For detailed workflows such as domain-based onboarding, sponsor approval, or Splash Page CSS customization, follow the linked guides rather than treating this page as a step-by-step guide to those features.
Create, edit, and assign a Login Profile
Go to Guest Wi-Fi → Setup → Login Profiles to create a profile or edit an existing one. Locations are initially provided with two profiles named Click-through access and Username and password. These are profile names, not enforced methods: the Sign-up setting determines the actual registration method.
To assign a profile to a Location, open Manage → Locations, select the Location, and select the Login Profile in its settings. Login Profiles can also be used with Passpoint Onboarding Portals.
Delegation to Location managers
Where a setting has a lock/unlock control, it determines whether the Organization-level configuration may be overridden at the Location level:
- Locked: the Organization-level value is enforced for the Location.
- Unlocked: the Location manager can change that value for the Location.
Delegation changes who may configure the setting; it does not change the setting's functional meaning.
Login options
The Login options tab defines the initial registration experience and the authentication choices presented on the Splash Portal.
Experience: Single-step or Multi-step
Start with Experience, because it determines which Primary Sign-Up settings are available.
| Experience | Behavior | Primary sign-up methods |
|---|---|---|
| Single-step | Registration uses one form. | Username/password, Click-through, or None. |
| Multi-step | Click-through onboarding uses two independently configured form steps. | Click-through only; Username/password is not available as the primary method. |
Changing the selected experience or sign-up method also changes which settings are visible in the editor. A hidden setting may still be supported in a different configuration.
Registration fields and required fields
Several registration methods expose two related selectors:
| Single-step label | Multi-step label | Purpose |
|---|---|---|
| Registration fields | Form Attributes | Chooses which personal-data fields are displayed. |
| Mandatory registration fields | Mandatory Attributes | Chooses which displayed fields must be completed. |
A displayed field that is not mandatory is optional. The required-field setting does not control whether a provided value is valid. Where available, a combined Phone or email requirement can be used. The selectable field list may differ between registration methods.
The standard Splash Portal selectors include Title, First name, Last name, Email, Birthday, Gender, Phone number, Personal ID, Personal ID (Brazil), Personal ID (Guatemala), Personal ID (Nicaragua), Passport number, Country, Zip/postal code, and Organization. For Username/password registration, leaving Registration fields unconfigured causes the platform's default registration fields to be requested.
Phone number validation. In native Splash Portal forms, the Phone number input already supports international country and calling-code selection. When a number is supplied, the platform validates it for the currently selected country when the user attempts to proceed or submit—not while the user is typing. Both valid mobile and fixed-line numbers are accepted. An invalid number blocks the action, marks the field as invalid, and displays “Please enter a valid phone number.” An optional Phone number field may be left empty; an empty mandatory field continues to use the normal required-field validation. This checks the number's formal validity, not whether it exists, receives SMS, or belongs to the user. It does not change the established format used to submit and store phone-number data.
Single-step: Primary Sign-Up
Under Primary Sign-Up → Sign-up, select Username/password, Click-through, or None.
Username/password
This method creates an account with credentials that users can use for subsequent sign-ins. Selecting it reveals the following options.
Username determines how the username is constructed:
| Option | Behavior |
|---|---|
| Phone number | Uses the registered phone number. When multiple accounts with the same number are allowed, a numeric suffix can distinguish usernames. |
| Username | Generates a name-based username from up to the first six characters of the first name and the first six of the last name, separated by a period, with a progressive number for uniqueness (for example, john.doe1). This option was formerly labeled Customer name. |
| Generated by the system | Assigns a system-generated alphanumeric username. |
Uses the email address; if the same email can be used by multiple accounts, a numeric suffix can distinguish usernames (for example, john.doe@example.com2). |
Other Username/password options are:
| Setting | Behavior |
|---|---|
| Allow sign-up from the Splash Page | Yes: users can register independently. No: users must obtain credentials through the Location manager or the Location's administration process. |
| Registration fields / Mandatory registration fields | Define which data is collected and which fields are required, using the shared rules above. |
| Allow multiple accounts with the same phone number | Yes: allows reuse within a Location. No: a number already assigned to an account is rejected until a different number is entered. |
| Allow multiple accounts with the same email | Yes: allows reuse within a Location. No: an email already assigned to an account is rejected until a different email is entered. |
| Show sign-up summary screen | Yes: after successful form validation, users can review the information and either continue online or return to edit it. No: the review screen is skipped. |
| Enable self-care portal | Makes My profile available so users can view and update their data, unregister, check active time policies, and consult past traffic sessions. |
| Allow password recovery from Splash Page | Yes: users can recover their passwords from the Splash Page. No: they must obtain help through the Location's credential-management process. |
Enable self-care portal and Allow password recovery from Splash Page are not available for Single-step Click-through. The sign-up summary screen is distinct from the Multi-step Back button described below.
Click-through
Click-through lets users register without creating a password. Registration fields and Mandatory registration fields determine which information is collected. Returning-user recognition is controlled separately under Advanced → Access Control → Authentication Methods; Click-through registration does not, by itself, imply automatic login on future visits.
Users who registered through Click-through may also receive persistent credentials and use the Sign In Form to access the service from other devices without registering again.
None
None disables the primary Username/password and Click-through sign-up methods. Select it when another enabled identification method is intended to provide access. No further primary sign-up settings are shown.
Multi-step: Click-through onboarding
Multi-step uses two separately configured Click-through screens. Each step can collect its own fields and display selected agreements defined under Policies.
Step 1
Configure Form Attributes, Mandatory Attributes, and Agreements for the first screen. Agreement choices include Terms & Privacy, Marketing, Age verification, and configured custom opt-ins.
Step 2
Configure its own Form Attributes, Mandatory Attributes, and Agreements. Fields and opt-ins may be included in both steps; values entered in Step 1 are pre-populated when those items appear again in Step 2.
Choose a Type to determine the available completion actions:
| Type | Behavior |
|---|---|
| Subscription | Shows Submit and Skip. The user may skip the optional second-step subscription or program. Selecting Submit requires any mandatory fields and agreements for that submission to be satisfied. |
| Enrichment | Collects additional information with Submit only; it does not offer the optional Skip action. |
For Subscription, Set Following opt-ins on subscription controls which opt-ins are associated with the subscription action. Configure the Step 2 Language, Title, and Sub-title to explain the purpose of the screen in each supported language.
Returning users. Step 1 is not necessarily displayed on every return visit. It can be shown again when required information is missing—for example, because a new field has become mandatory—or when optional data is being requested and Advanced → Other → Skip Optional Data Prompt for Returning Users is disabled. Otherwise, a returning user may proceed directly to Step 2.
Back navigation. Step 2 supports a Back button in both Subscription and Enrichment flows. It is hidden by default and must be made visible through custom Splash Page CSS. When enabled, it appears only if Step 1 was actually displayed during the current flow; it remains absent when Step 1 was skipped. Clicking Back returns to Step 1 without losing the information already entered. For the CSS rule and setup instructions, see Splash Pages advanced personalization via CSS.
Sign In Form: credentials in a Click-through experience
The Sign In Form adds a username/password sign-in choice to a Click-through Splash Portal. It allows users who already have credentials to sign in without registering again—for example, on another device or when MAC address randomization prevents recognition of a previously used device. Issuing or distributing persistent credentials is separate from enabling the form.
Under Sign In Form, set Enable to Yes and select an Experience Mode:
| Experience Mode | Behavior |
|---|---|
| In Form | The username/password form appears directly below the Click-through form. If SSO buttons or a Kiosk access-code form are configured, they appear below the username/password form. |
| Button | A Log in with your account link appears directly below the Click-through form. Selecting it reveals the credentials form and hides the other authentication elements, including the Click-through form, SSO buttons, and any Kiosk access-code form. |
In Button mode, the link uses the same styling as the SSO buttons to support consistent CSS customization. Neither mode replaces Click-through as the primary registration method. See Persistent Credentials: The Solution for Multi-Device and Long-Term Access for credential provisioning and use.
External Service IDP (Social Login)
Use External Service IDP → Enable to offer authentication through configured external identity providers. The available provider controls include Apple ID, Facebook, LinkedIn, Twitter (X), Gmail (Google), VKontakte, and Yahoo. Where supported, an Apple-specific display setting can limit the Apple option to Apple devices.
Registration fields specify information to request if the identity provider does not return it; Mandatory registration fields make selected information required. Native Splash Portal field validation—including Phone number validation when the field is presented—also applies. Additional verification can be configured under Advanced → Access Control → Social Login Verification.
Kiosk: One-time password login
The Kiosk section appears when the Kiosk application is enabled under Manage → Extensions → Apps. Enabling the application exposes its Login Profile settings; it does not enable One-time password login automatically.
Set One-time password login to Enabled to use it. Kiosk has its own Registration fields and Mandatory registration fields, with a smaller field set than standard Splash Portal registration: Title, First name, Last name, Email, Birthday, Gender, Phone number, Country, Zip/postal code, and Organization. Other controls include Send OTP code via text message, Sponsor notification via email, and Sponsor notification via text message. See the Kiosk documentation for the dedicated Kiosk workflow.
Advanced
The Advanced tab contains domain-based rules, returning-user authentication, verification and sponsor approval, communications, and post-login behavior.
Domain Based Onboarding
Domain Based Onboarding applies onboarding and access rules based on the user's email domain. Depending on the configuration, matching users can be assigned to destination groups (when Group Policies are enabled), restricted to configured domains, or allowed temporary access while completing email verification.
Allow access to listed domains only determines whether access is restricted to the configured email-domain list (Yes) or is not restricted solely to that list (No). Network Access Allowance determines whether a user receives temporary access to check email during validation (Give temporary access to check email) or must complete validation without such access (Don't give temporary access to check email).
Domain-based rules take precedence for users matching those rules. The Access Control settings below apply to users outside the domain-based onboarding rules. For detailed setup and domain-matching behavior, see Domain-based Onboarding.
Access Control
Authentication Methods
Authentication Methods determines the experience for returning users, independently of the method originally used to register.
| Method | Returning-user behavior |
|---|---|
| Classic | Presents the regular Splash Page on each visit. It does not provide recognition-based automatic login or a one-click reconnection action. |
| One-Click Login | Recognizes returning devices by MAC address and offers connection with one click, regardless of the original sign-up method. This helps avoid repeat registration through a different method and duplicate contact records. |
| Auto-Login | Recognizes returning devices by MAC address and authenticates them automatically when they reach the Splash Page, without requiring an additional action. |
MAC address randomization can prevent recognition of a device that previously connected. Auto-Login requires the network equipment to provide the device MAC address and was formerly called Smart Authentication. It should not be confused with network-level MAC authentication, which may bypass the Splash Page entirely. See Auto-Login options for returning users for technical requirements.
Primary Sign-Up Verification
Primary Sign-Up Verification adds a verification step after primary registration. The available choices depend on the sign-up method:
| Verification | Username/password | Click-through |
|---|---|---|
| None | Yes | Yes |
| Password via text message | Yes | — |
| Inbound text/call | Yes | — |
| Link via email | Yes | Yes |
| Link via text message | Yes | Yes |
| Code via text message | Yes | Yes |
Password via text message sends the password to the supplied phone number. Inbound text/call requires the user to send a message or call a designated number to obtain credentials; Enable inbound call and Enable inbound text messages control these channels separately. With an email or SMS verification link, or an SMS code, users must complete the relevant verification step before obtaining access.
These verification methods must not be confused with Phone number format validation, which does not establish ownership or SMS reachability. Primary Sign-Up Verification is incompatible with Sponsor Validation and with certain other verification or domain-restriction settings, as indicated in the editor.
Social Login Verification
Social Login Verification adds a verification step following authentication through an external identity provider. Available choices are None, Receive code via text message, Send a text or call, and Link via text message. The editor prevents combinations that conflict with Sponsor Validation or Double Opt-in.
Other access requirements
Require access code for foreign users requires an additional code when the country calling code of the user's phone number differs from the account's default country code. Choose Yes to require it or No not to require it.
Shared password requires an additional common password after successful authentication and before network access is granted. It cannot be used together with Sponsor Validation.
Sponsor Validation
Sponsor validation requires authorization from an eligible sponsor before the guest gains access. It provides these modes:
| Mode | Behavior |
|---|---|
| None | Disables sponsor approval. |
| Single Sponsor | Uses a single configured sponsor email address. |
| Multi Sponsor | Permits sponsors whose email domains match the configured permitted domains; the domains are entered as a comma-separated list. |
| Select from list of sponsors | Lets the user select a sponsor from a predefined list. |
Compatibility: enabling Sponsor Validation disables Primary Sign-Up Verification, Social Login Verification, Require access code for foreign users, and Shared password. It is also incompatible with Allow access to listed domains only. These relationships matter when interpreting disabled settings in the editor. See Sponsor validation for the complete approval workflow.
Communications
| Setting | Behavior |
|---|---|
| Send welcome email at sign-up | Sends a welcome email after the user registers. |
| Send welcome email once logged in | Sends a welcome email when the user signs in. |
| Send text message with the credentials | When available for the selected authentication or verification flow, sends credentials by SMS. |
Sending credentials is different from enabling the Sign In Form. A visible credentials form does not, by itself, generate or distribute credentials.
Success Page
Display welcome box on landing page controls whether a welcome box appears after successful authentication.
Show log out button, where supported by the network vendor and selected authentication mode, allows Logout buttons or links to appear on the Splash Page. The option may be unavailable when web-based logout is unsupported or inappropriate for the selected mode—for example, Auto-Login.
Other
Skip Optional Data Prompt for Returning Users (Yes/No) controls whether returning users are prompted solely to provide optional information. Enabling it skips optional-data prompts but does not waive newly required fields. In a Multi-step flow, it therefore also affects whether a returning user sees Step 1.
Bypass Apple CNA (Yes/No) is available for environments that need to bypass the standard Apple Captive Network Assistant flow. Its applicability depends on the captive-portal integration.
Policies
The Policies tab defines the content, presentation, acceptance requirements, and versioning of service agreements. In Multi-step configurations, the Agreements selector on each step controls where a configured clause appears; the clause itself is managed here.
Terms of Use and Privacy Policy
Acceptance of Terms of Use and Privacy Policy controls how acceptance works:
- Explicit: users must check the relevant acceptance box before continuing; otherwise, they receive a validation error.
- Implicit: continuing to access constitutes acceptance, and the Splash Page presents an explanatory statement instead of an acceptance checkbox.
Terms of use and Privacy Policies controls how the clauses are grouped:
- Unified in single clause: one combined statement covers both documents.
- Two independent clauses: Terms of Use and Privacy Policy are displayed as separate statements.
The two settings are independent: Explicit/Implicit is the acceptance mechanism, whereas Unified/Two independent clauses controls presentation.
For Terms of Use and Privacy Policy separately, choose Default text or Custom text. Custom text can be localized into the supported Splash Page languages and requires a Version. Ask your existing users to accept the new policy version again requires users to re-accept a policy if their previously accepted version differs from the configured version. Because this can affect returning users, use it intentionally. See the policy re-acceptance guide for details.
Pre-check Terms of Use and Privacy Policy determines whether acceptance checkboxes are initially selected where they are displayed. Choose settings that comply with the applicable consent requirements.
Promotional Communication Policy
Promotional Communication Policy determines how users are offered a marketing-consent choice:
| Setting | Behavior |
|---|---|
| No | No marketing choice is shown, and users do not receive promotional communications through this service. |
| Opt-in to receive promotional communications | Users are asked to indicate agreement to marketing communications by selecting the checkbox. |
| Opt-out of receiving promotional communications | Users are offered a choice to decline marketing communications; leaving the checkbox unselected indicates that they do not accept marketing. |
When a marketing choice is enabled, the clause may use Default text or localized Custom text. The configuration can include Version, Ask your existing users to accept the new policy version again, and Require the acceptance. Pre-check Promotional Communication Policy controls the initial checkbox state when available for the selected Opt-in configuration.
Enable Double Opt-in changes when marketing consent becomes active. If a user accepts marketing, the acceptance must then be confirmed through an additional communication before the consent is activated:
| Value | Confirmation behavior |
|---|---|
| No | No second confirmation is required. |
| Via email | Marketing consent becomes active only after the user confirms it through a separate email. |
| Via phone | Marketing consent becomes active only after the user confirms it through a separate phone-based communication. |
Double Opt-in may disable incompatible verification settings in Advanced → Access Control. The editor indicates those conflicts.
Minimum Age Verification
Enable Minimum Age Verification to ask users to confirm that they meet the service's configured age requirement. Supply the clause and a Version, and enable Ask your existing users to accept the new policy version again when a changed version must be acknowledged. See the policy re-acceptance guide for the versioning behavior.
Custom Opt-ins
A Login Profile supports up to five custom opt-in clauses. Each includes:
| Setting | Purpose |
|---|---|
| Name | Internal alphanumeric identifier (letters and numbers only), used for inventory and exports rather than as visible clause text. |
| Version | Identifies the current clause version. |
| Label | User-facing clause text, provided in the supported Splash Page languages. |
| Required | Makes acceptance mandatory when the clause is presented. |
| Ask your existing users to accept the new policy version again | Requests re-acceptance after a version change. |
The platform stores the recorded acceptance, which is available in user-data exports from People. In a Multi-step experience, choose where each custom clause appears under the relevant step's Agreements selector.
Related documentation
- Click-through in detail — Click-through registration and data collection.
- Auto-Login options for returning users — device recognition and technical requirements.
- Persistent Credentials: The Solution for Multi-Device and Long-Term Access — credentials for users initially registered through any method.
- Splash Pages advanced personalization via CSS — how to display the optional Multi-step Back button.
- Validating end-users' phone number using a confirmation code — verifying a number via SMS, distinct from format validation.
- Domain-based Onboarding and Sponsor validation — specialist onboarding and approval workflows.
- Policy re-acceptance guide — asking existing users to accept revised clauses.