Selecting the branch, you are displayed the list of registered users to the domain.

Allows you to add a new gateway depending on the authentication method chosen in the domain
This option is not possible if:

• The licence limits have been reached;
• The limit of the gateways’ number, defined in the manager or reseller have been reached
• You do not have permissions to add.

Allows you to add a new user to the domain.

Option

Description

Card Management

Opens the card management page. Active only for domains with the following “authentication modes”: with SMS sending from the user; with registration by the user, with registration by the operator.

Selecting the branch, you will open the domain’s dashboard with the following tiles: the main chart; connections, traffic, new users, users, GW sold, domains with most connections, users with most traffic; social users; context data.
For further details about the content of the various tiles, please refer to the “Tile Types of the Dashboards“ paragraph.

 Display all Connected Users

Shows in a table, all the users connected to the gateway of the domain.

 Display all Users

Shows all users registered to the domain.

 List of Access Points

Opens the page containing the list of all the access points entered at domain-wide level.

Opens the page containing the list of all the gateways entered at domain-wide level.

Shows the map of all configured gateway based on their GPS coordinates.

 Sales to Users

Shows in a table, grouped by manager, product, month and year, the costs and the revenue developed by the managers for the sales of connectivity to users.

Opens the page for managing domain-wide data. 

Shows the “Voucher” management page. Not active for domains with the “Without registration” “Authentication Mode “

Option

Goes to the management of the custom apps and specific per domain or per gateways associated with it. To make them visible in the Welcome Portal you should assign them in the configuration of the domain or of the gateways.

Opens the home page for managing custom images for the domain. You can use them in the current domain and in gateways associated with it.

Allows you to define the images of all the languages and also the parameters for the additional languages

Available only in the Enterprise edition.

Opens the page for managing surveys, quizzes and tests.

Templates

Allows you to manage the templates that customise the Welcome Portal for the domain and the gateways.

Allows customisation, for the domain and the gateways, of the texts displayed in the Welcome Portal, in the standard apps and in the printing of “ Cards” or to add texts for additional languages.

Allows you to define the accessible URLs by users of the domain and of the gateways without logging in and registering

ID of the record. Auto-assigned Identifier of the record. It can be used to use the API or external integrations.

Editable only if the user has permissions to manage the domain data.

Name of the domain.

Editable only if the user has permissions to manage the domain data.

Defines the user authentication mode. If you choose PPPoE for users, login and registration are not provided. The administrator must manually create users in Network Station and then configure the router. In this case, the appliance will act as a radius server for the PPPoEs. This option is not editable if you have selected PPPoE and there are already registered users. Possible values are:

Click & connect. No registration, no password: the gateways belonging to this type of domain will allow the user to surf without registration. In practice, the same login request will appear to the user displays but without the possibility to enter username and password that is the same for all users and automatically inserted.

By selecting this authentication method, when it saves the data, it will create a user “free” with a random password. You can change any user’s field (including the password) into the user’s editing.

If you want to use this type of authentication, it is necessary that:

• The product chosen for the domain (see section “Products for the domain” further on this section) has a product policy (see “Product Policies” paragraph) with the “Concurrent Connections” field greater than 1 (if not, only a user at a time will manage to connect to the gateway).
• The product chosen for the domain has a specified price equal to 0, both in the domain definition and in the product (see the paragraph “Products“).

To the “free” user, which has automatically been created when creating the domain, it will be assigned the first free product attributes defined in the domain.

QR Code & connect. No registration, no password: GWHs that are part of this type of domain will allow the user to navigate without the need to register by scanning a printable QR Code from the context menu of the gateway or access points.

After scanning the QR Code with the Camera App, the user will not be prompted to open the URL. While clicking, the user will be redirected to the Welcome Portal and then automatically connected.

As for “Click & connect. No registration, no password”, when data are saved, a “free” user will be automatically created with a random password.

This authentication mode is not compatible with Fortinet type of gateways.

Simple password. No registration: this type of domain is equal to the previous one but on the login page, the user must enter a password, which must be required to the manager (this password is the one defined in the “Password for login” field)

It is useful if you want to provide free internet access without the necessity to register to the service, but avoiding that anyone uses the connection. Only those who know the password can access to the internet.

The manager may at any time change the login password.

With sending an SMS by the user: the gateways that use this type of authentication, allow the user to subscribe to the service by sending an SMS to the number indicated in the registration process and configured in “System Settings” (this setting is only available for the administrator of the system).

In this way, it will automatically create the user with a username equal to the mobile number from which the SMS has been sent. Credentials for login will be returned to the user via e-mail or SMS, and then you have to enable at least one of the options “send SMS notification” and/or “Send mail notification” unless you enable the option “User password by SMS.” In this case, the user who wants to register to the service can send an SMS to the number notified by the hotspot provider, editing an SMS text, after the domain name, a space, and the password to be assigned in the form: Domainname [space] Mypassword. In this way, a user will be automatically created, equal to the mobile phone number from which the SMS has been sent, with a password included in the sent message.

This type of domain is useful to avoid the data registration by the users and possibly avoid the SMS sending with credential by the system (this is possible only if the options “Send mail notification” or “User password by SMS” are enabled).

With registration by the user: the user must register with the service, following the procedure initiated by the button “Register” that among the steps requires filling of the provided fields. The fields that the user is required, will be selected in the section “Data to customise user registration” explained below. This type of domain is useful if you want to record the users’ log data about user.

Also, for this type of domain, it is possible to send the login credentials both via SMS and via e-mail based on enabled or disabled fields “Send SMS Notification” and/or “Send Email Notification”.

The product chosen by the user, if not a free product, it can be paid through one of the enabled gateways for payments.

With registration by the user without password:  it uses the same modes of “With registration by the user”, but user does not have to insert the password.

Warning! This method simplifies the login, but user authentication is not secure and there may be any conflicts with the security policies. If a user knows the email of another user, he will be able to access.

With social registration by the user: it uses the same modes of “With registration by the user”, but user must register and login only through social network.

Warning! To use this option user must enable the social networks.

With operator registration: the gateways belonging to this type of domain will allow the user to use the service only after have been registered by the Manager. With this type of domain, the user will not be able to “auto register” because the login page will not display the “Register” button. The manager must manually register the user (click the context button above the domain in the “data” tab and select “ Add user”) and then print the card with the login credentials by clicking the appropriate button in the upper right corner.

In this type of domain, if the product provided to the user, has a cost, the user has to pay it directly to the manager.

During user’s registration, the manager will be proposed the products defined in the section “Products for the domain” explained below.

OTP (One Time Password or single use password) sent via SMS: similar to “With registration by the user” but at every login, a new password is sent to the user. The login App will only show the field to enter the mobile phone number. Once entered, the system will check if it has already registered and if so, it sends a new password to the user. User must enter the password when required. If the phone number has not already been registered, the system goes directly to registration if you have activated the “Auto registration” check for non-existent credentials.

The password sent to the user is valid for two minutes. If not used within the time limit, another one will be sent to the next login.

PPPoE: this type of domain is selected when you need to use Network Station as RADIUS server with PPPoE connections. In this case, for users, registration and login are not provided as credentials must be configured directly into the router on in PPPoE client of the user.

The manager must manually register the user (click the context button above the domain in the “data” tab and click “Add user” ).

This “domain Authentication mode” is not editable if you have selected PPPoE and there are already registered users.

WPA Enterprise: it allows the authentication of users via the WPA2 protocol with the RADIUS support.

In this case users are not redirect to the Welcome Portal but the devices automatically request the username, the password and any security certificate.

You can download the certificate from the dropdown menu of the WPA Enterprise gateway.

As for the PPPoE connections, the manager needs to manually registrate the user (from the “Data” tab click the dropdown menu of the domain and click on “ Add user”).

Editable only if the user has permissions to manage the domain data.

The domain is federated with the defined federation groups. Users are shared among all the domains that are part of the groups. If a user attempts to log in to a domain on which his credentials do not exist, the system will automatically check if his credentials exist on one of the other federated domains and if so, allows the login.

Warning! Federated domains must have the “authentication mode” compatible and that require the same type credentials for logging in. For example, a domain that requires only the user name is incompatible for federation with another domain that requires the username and password.

Password for Login

Password to be provided to users for login.

The field is displayed and used, only if you have selected the authentication mode “Simple password. No registration

Welcome Portal Template

Declares the template to use for this domain, which parameterises the contents and graphic form of the Welcome Portal or of the login page. If you enable the option “Use default”, it will use the default template defined in “General Options” (this option is only available for the administrator of the system).

Any template imposed in the gateway takes precedence over this value.

Specific products for the manager are displayed in white, specific products for the reseller or for the manager in light blue and general products in brown

Selectable templates are coloured in base to the level they belong to. In specific, custom templates for the domain are displayed in light blue and in yellow ochre the ones for the system.

Template Color Scheme

Colour scheme to use for the selected template.

If you enable the “Use default” option, you will use the colour set in the “General Options” (this option is only available for the administrator of the system).
Any template imposed in gateway takes precedence over this value.

Defines the type of user interface to use for the login.

The possible choices are:

Welcome portal lite: reduced version of the Welcome Portal without App bar, standard Apps and Advertising.

Welcome Portal: full version of the Welcome Portal with App bar, standard Apps and advertising support.

Option “Without Welcome Portal” is no longer available on Network Station with system versions greater than or equal to 1.7 because replaced by Welcome Portal Lite

The type “Welcome Portal” is available only if you have purchased the licence for the “Welcome Portal”.

Defines the type of advertising, derived from ”  Advertising Campaigns“, viewable to users.

Possible values are:

• Enable: enables the inclusion of advertising:
• Only for campaign on this domain: enables the inclusion of advertising only for specific campaigns for this domain (they must have defined the domain field).
• Disable: does not display the advertising.

Editable only if the user has permissions to manage the domain data.

Surveys, Quizzes or Tests

Enables the request for surveys, quizzes or tests.

Possible values are:

• Enable, one at a time. Enables the request to fill in the surveys but at maximum one at a time.
• Enable, all those provided. If the current context provides multiple surveys, users will be asked to fill them all.
• No surveys are required and it does not consider anything defined in the gateway.

Editable only if users have permissions to manage the domain data.

If required, API Key of the ERP or PMS to be integrated.

Some ERPs/PMSs require an API Key in order to accept or submit requests. If necessary, also based on supported ERPs/PMSs, enter the API Key.

If required, API Secret of the ERP or PMS to be integrated

Some ERPs/PMSs require an API Key and an API Secret in order to accept or submit requests. If necessary, also based on supported ERPs/PMSs, enter the API Secret.

Enable the FIAS protocol (Fidelio Interface Application Specification).

Allows you to exchange data with many PMSs that have adopted these specifications. The main features supported are the creation of users at the check-in, the disabling of users at the check-out, the charge at the check-out when purchasing additional products, the change of credentials when changing a room or information about the same.

Warning! In order to enable FIAS, you must have the relevant license .

IP Addresses for FIAS

List of IP addresses, separated by comma, from which to accept FIAS requests.

All connection requests that come from IP addresses that are not listed, are discarded

IP Port for FIAS

IP port for data exchange with FIAS protocol

The value must be between 1025 and 65535

Each domain must have a different port. No duplicates are allowed in the system.

Resynchronise with FIAS

It enables the “Complimentary access” login by users without asking a registration. When the time/traffic assigned to the product runs out or expires, a registration will be required.

Request Acceptance of Conditions at Login

It requires the acceptance of the contractual terms and conditions for each user’s login.

Password to provide to users in order to make the “Complimentary Access”.

If not specified, user will not be forced to enter the password.

Product to assign to users who are using the “Complimentary Access”.

Editable only if user has permissions to write the domain’s products.

It defines whether you can reassign the product upon expiration or exhaustion of the time or of the total traffic.

The possible options are:

• Never;
• At expiration or at exhaustion of time credit and/or total traffic;
• At expiration.

Editable only if user has permissions to write the domain’s products.

Popup Injection

It allows you to enter advertising popups in the Welcome Portal and in the pages viewed by users during web surfing.

The possible options are:

• Disable: disables the injection.
• Enable: enables the injection.

Warning! Injection works only if advertising module is active and advertising campaigns have been entered with content for injection.

Time of First Popup

Defines the number of seconds that must pass before the first insertion of popup.

Popup Frequency

Defines the frequency of the popup calculated in seconds.

Display in the Welcome Portal

If enabled, popups are injected also in the Welcome Portal.

Display the Toolbar

States whether to display the toolbar that allows the user to return to the Welcome Portal while browsing.

Requires the use of CO.IN.

List of the system apps to load for this domain.

To select the App, open the list by clicking in the field and make your selection. To remove an App already selected, click the  button in the App already loaded.

Besides the specific App for domain (press the button on the domain properties and choose “ Custom app “) and for the gateway (press the button of properties on HGW and select “ Custom app”), it uploads also the system Apps defined in this field.

If you do not want to upload one or more App of the domain or of the gateway, click the button of the App properties and select “ Lock/Unlock” to block uploading.

To check the system Apps, press the button of properties on “System” and select  ”  Custom app”.

Request Username

Require the user’s username, during the registration process.

The possible options are:

• Self-generated: no data are required to the user, the name is self-generated.
• Use the MAC address: no data are required to the user, the username corresponds to the MAC address of the device.

• Use the mobile number: the username corresponds to the mobile number. The mobile number request must be enabled.
• Use the mobile number: self-generated with a social network registration: if user registers via social network, name is self-generated.
• Entered by the user: User can define his own username.
• Entered by the user: self-generated via social network registration: if user registers via social network, the username is not required but it is self-generated.
• Use the email address: user has to enter a valid email.
• Use the email address: self-generated through a social network registration: if user registers through a social network, the email address is not required but it is self-generated.
• Use the room or pitch number (only for integration with ERP/PMS). Generally, this type of username is used only for the integrations with ERP/PMS and it is set only for these purposes and not leaving the users the possibility to edit. If you use this option to make always the users enter the room number in the user registration mode, the user will not be able to auto register if the operator has not deleted the previous user. If the user will be recreated by an ERP/PMS, the previous user data will be overwritten and the purchase story, the used device and the connections made will be deleted.

The field is only available if the authentication mode is “With registration by the user” or “With registration by the user without password”.

If the registration mode is “Sending an SMS by the user”, the “entered by the user” and “require an email address” options are enabled only if registration has been done through a social network and not considered if user sends an sms. If you select one of these options and the user sends an sms, the username will be auto generated.

Request the Mobile Number

Require the user’s mobile number, during the registration process.

The possible options are:

• No: mobile number is never required;
• Yes: mobile number is always required; automatically enabled if in the field “Request the Username” has been defined the option: Use the mobile number.
• Yes, but not with registration via social network: if user logs in via a social network, the mobile number is not required.
• Yes not mandatory: mobile number is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is only available if the authentication mode is “With sending an SMS by the user”, “With registration by the user”, “With registration by the user without password”, “With social registration by the user” or “With operator registration”.

Request the Password

Require the user’s password, during the registration process..

The possible options are:

• Self-generated: password is never required to the user. It will be automatically generated.
• Yes: password is always required. If the user is created by an ERP/PMS, the password will be requested to the user at the first login.
• Yes, but not with registration via social network: if users logs in via a social network, password is not required.
• Yes not mandatory: password is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

• Use the last name (only for integrations with ERP/PMS).
• Use the first name (only for integrations with ERP/PMS).
• Use the mobile number (only for integration with ERP/PMS).
• Use the email address (only for integration with ERP/PMS).

For integration with ERP/PMS, if you specify to request the password to the user, the ERP/PMS will not create the password but it will be requested to the user at the first login.

The field is only available if the authentication mode is “With registration by the user”.

If in the “ System Settings” the Password Encryption has been enabled, users can enter password (Unicode) with all character sets. If not enabled, sers can use only alphanumeric and “+-*/=_.,;:$#&@<>|~\^()[]{}!?”characters.

Request the Company Name

Require the user’s company name, during the registration process.

The possible options are:

• No: company name is never required;
• Yes: company name is always required.
• Yes, but not with registration via social network: if user logs in via a social network, the company name is not required.
• Yes not mandatory: company name is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the Gender

Require the user’s gender, during the registration process.

The possible options are:

• No: gender is never required.
• Yes: gender is always required.
• Yes, but not with registration via social network: if user logs in via a social network, gender in not required.
• Yes not mandatory: gender is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without registration”

Request the First Name

Require the user’s first name, during the registration process.

The possible options are:

• No: name is never required.
• Yes: name is always required.
• Yes, but not with registration via social network: if user logs in via a social network, first name is not required.
• Yes not mandatory: first name is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the Last Name

Require the user’s last name, during the registration process.

The possible options are:

• No: last name is never required.
• Yes: last name is always required.
• Yes, but with registration via social network: if user logs in via a social network, last name is not required.
• Yes not mandatory: last name is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “ Without Registration”.

Request the Address

Require the user’s address, during the registration process.

The possible options are:

• No: address is never required.
• Yes: address is always required.
• Yes, but not with registration via social network: if user logs in via a social network, address is not required.
• Yes not mandatory: address is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the ZIP Code

Require the user’s ZIP code, during the registration process.

The possible options are:

• No: ZIP code is never required.
• Yes: ZIP code is always required.
• Yes, but not with registration via social network: if user logs in via a social network, ZIP code is not required.
• Yes not mandatory: ZIP code is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the City

Require the user’s city, during the registration process.

The possible options are:

• No: city is never required.
• Yes: city is always required.
• Yes, but not with registration via social network: if user logs in via a social network, city is not required.
• Yes not mandatory: city is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the State/Province

Require the user’s state/province, during the registration process.

The possible options are:

• No: state/province is never required.
• Yes: state/province is always required.
• Yes, but not with registration via social network: if user logs in via a social network, state/province is not required.
• Yes not mandatory: state/province is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the Country

Require the user’s country, during the registration process.

The possible options are:

• No: country is never required.
• Yes: country is always required.
• Yes, but not with registration via social network: if user logs in via a social network, country is not required.
• Yes not mandatory: country is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the Day of Birth

Require the user’s day of birth, during the registration process.

Possible options are:

• No: day of birth is never required.
• Yes: day of birth is always required.
• Yes, but not with registration via social network: if users log in via a social network, day of birth is not required.
• Yes not mandatory: day of birth is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the Month of Birth

Require the user’s month of birth, during the registration process.

Possible options are:

• No: month of birth is never required.
• Yes: month of birth is always required.
• Yes, but not with registration via social network: if users log in via a social network, month of birth is not required.
• Yes not mandatory: month of birth is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the Year of Birth

Require the user’s year of birth, during the registration process.

Possible options are:

• No: year of birth is never required.
• Yes: year of birth is always required.
• Yes, but not with registration via social network: if user logs in via a social network, year of birth is not required.
• Yes not mandatory: year of birth is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Minimum Age

Minimum age allowed for registration and to use this service.

In order to enable this limitation, it is necessary to request the year of birth.

Request the Fiscal Code/VAT-Id Number

Require the user’s fiscal code/VAT number, during the registration process.

The possible options are:

• No: fiscal code/VAT is never required.
• Yes: fiscal code/VAT is always required.
• Yes, but not with registration via social network: if user logs in via a social network fiscal code/VAT is not required.
• Yes not mandatory: fiscal code/VAT is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the Email Address

Require the user’s email address, during the registration process.

The possible options are:

• No: email address is never required.
• Yes: email address is always required.
• Yes, but not with registration via social network, if user logs in via a social network, email address is not required.
• Yes not mandatory: email address is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the Phone Number

Require the user’s phone number, during the registration process.

The possible options are:

• No: phone number is never required.
• Yes: phone number is always required.
• Yes, but not with registration via social network: if user logs in via a social network, the phone number is not required.
• Yes not mandatory: phone number is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request the Fax Number

Require the user’s fax number, during the registration process.

The possible options are:

• No: fax number is never required.
• Yes: fax number is always required.
• Yes, but not with registration via social network: if user logs in via a social network, the fax number is not required.
• Yes not mandatory: fax number is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request Room/Pitch Number

Require the user’s room/pitch number, during the registration process.

The possible options are:

• No: room/pitch number is never required.
• Yes: room/pitch number is always required.
• Yes, but not with registration via social network: if user logs in via a social network, the room/pitch number is not required.
• Yes not mandatory: room/pitch numer is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Marketing Consent

Require the user’s consent for marketing activities, during the registration process.

The possible options are:

• No: marketing consent is never required.
• Yes: marketing consent is always required.
• Yes, but not with registration via social network: if user logs in via a social network, marketing consent is not required.
• Yes not mandatory: marketing consent is not a mandatory field..
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Newsletter Consent

Require the user’s consent for sending the newsletters, during the registration process.

The possible options are:

• No: newsletter consent is never required.
• Yes: newsletter consent is always required.
• Yes, but not with registration via social network: if user logs in via a social network, newsletter consent is not required.
• Yes not mandatory: newsletter consent is not a mandatory field.
• Yes not mandatory but not with registration via social network: it is not mandatory but the registration via social network is not required.

The field is not available if the authentication mode is “Without Registration”.

Request a CAPTCHA Code

Require CAPTCHA validation code, during the registration process.

The possible options are:

• No: captcha code is never required.
• Yes: captcha code is always required.
• Yes not mandatory: CAPTCHA code is not mandatory.
• Yes, but not with registration via social network: if user logs in via a social network, captcha code is not required.

It is needed to prevent non-human registrations and therefore attacks of bots that could register users without completing the normal procedure.

The field is not available if the authentication mode is “Without Registration”.

Request Acceptance Conditions

Require the acceptance of terms of use and conditions, during the registration process.

The possible options are:

• No: users are not requested to accept terms and conditions.
• Yes: users are always requested to accept terms and conditions.
• Yes, also at every login: users, in addition to be always requested to accept terms at the registration, they are always requested at each login.

If you enable the “Requiest Acceptance Conditions at Login”, user will be anyway requested to accept the conditions.

Request Acceptance of Conditions at Login

Requires the acceptance of the contractual terms and conditions at each login that the user performs.

The field is not available if the authentication mode is “Without Registration”.

Request Acceptance of Privacy Policy

Requires the acceptance of the privacy policy conditions.

The possible options are:

• No: users are not requested to accept.
• Yes: users are always requested to accept.

In order to fulfil the GDPR (General Data Protection Regulation UE 2016/679) user must give his unequivocal informed consent therefore we recommend to define “Yes” in this field.

The field is not available if the authentication mode is “Without Registration”.

Auto Registrazione for Non-Existing Credentials

When enabled, if users enter incorrect or non existing credentials, they are automatically redirected to registration.

The field is not available if the authentication mode is “Without Registration”.

Show Credentials

At the end of registration, it enables the display of login credentials (Username and password) for the user.

The available options are:

• No: it never displays the credentials.
• To all: it always displays the credentials.
• Only to domestic calling country codes: it displays credentials only to domestic codes or accepted foreign codes.
• Only to foreign codes: it displays credentials only to foreign or not accepted country codes.

Warning! Credentials are displayed if the SMS sending is not intended.

Please refer to “Accepted foreign phone codes” paragraph for explanations and definitions on domestic and international codes.

The field is not available if the authentication mode is “Without Registration”.

Display the Registration Confirmation

At the end of the registration, a form appears with the successful registration message.

If the international calling code with which the user is registering, is not among the ones accepted, the redirect is enabled to an external page and the display of the credentials is disabled. Anyway, the registration confirmation will be displayed to perform the opening of a new tab. Without the “click” by the user, the tab would not open due to security restrictions of the browsers.

The field is not available if the authentication mode is “Without Registration”.

Request Missing Data

If enabled and the user profile is incomplete according to the requested data, the user is asked to complete the missing data at the next login.

The required data may be incomplete for various reasons:

• The requested fields have been changed in the domain;
• The operator has created the user but has not completed all the required fields in the domain;
• The user registration has been performed via API/PMS but some requested fields have not been passed.

Possible values are:

• No: it never requires the missing data;
• Yes, only if mandatory fields are missed: it requires data only if mandatory fields have not been filled in;
• Yes: it always requires missing data.

The field is not available if the authentication mode is “Without Registration”.

Display in case of Missing Data

If you want to request to the user some missing data, this option allows you to define whether to show the already entered data:

The possible options are:

• Only missing fields;
• All the fields. Disable the completed ones.
• All the fields. Editable even the completed ones.

The field is visible only if in the “Request Missing Data” filed, you have selected “Yes, only if mandatory fields are missed” or “Yes”.

The field is not available if the authentication mode is “Without Registration”.

Auto-Login at Registration or Recharge

At the end of the registration or of the recharge, it performs the auto-login without asking the user to press the appropriate button.

Warning! Enabling this option, it will no longer be possible to require the user to press “Like”, “Follow” or share the location on social networks at the end of the registration.

It is not performed if the user has entered an international calling codes not accepted.

It is not visible if the authentication mode is “OTP (One-Time Password) sent via SMS.

The field is not available if the authentication mode is “Without Registration”.

Auto-Surf at Login

At login, it redirects automatically the user to the URL requested by the same user or to one of the URLs defined in the “Redirect URLs” field.

Warning! “Redirection” can not be used with CNA.

The field is not available if the authentication mode is “Without Registration”.

Custom URL for Data Validation

Enter the custom URL of the page that will have to validate the user’s registration data. The page will have to make the appropriate verifications on data entered by the user and will have to return any code and error description.

For further details about how to integrate with an external validation system, please, refer to the “Developer Manual” at the “Custom Validation of the User’s Registration Data” chapter.

The field is not available if the authentication mode is “Without Registration”.

Username Mask

Mask for generating usernames. It can include X uppercase alphanumeric; x lowercase alphanumeric; C uppercase consonant; c lowercase consonant; V uppercase vowel; v lowercase vowel; N or n numeric (no zero).

If not defined, it uses the ones specified in “System Settings”.

Define at least three valid characters.

Warning! A too restrictive mask on a domain that will contain many users could cause registration problems.

Password Mask

Mask for generating passwords. It can include: X uppercase aphanumeric; x lowercase aphanumeric; C uppercase consonant; c lowercase consonant; V uppercase vowel; v lowercase vowel; N or n numeric (no zero).

If not defined, it uses the ones specified in “System Settings”.

SMS Confirmation Request

To confirm registration, it requires the user to send an SMS, writing in the text the domain name.

The available options are:

• No;
• To all;
• Only to domestic codes;
• Only to domestic codes or accepted foreign codes;
• Only to foreign codes;
• Only to foreign codes and not accepted.

If enabled, after the user clicks the “Register” button on the login App, he will see a message saying “now, please send a confirmation SMS to the number xxxxxx with written NomeDomain in order to validate the entered data”. After, by pressing the “next” button, he can register and the user will be active as soon as Network Station receives the SMS.

If the SMS has not been received, the user will be registered but will not be active and not be able to surf.

If in the domain, you have enabled the “Send SMS notification” and/or “Send mail notification” check, as soon as Network Station receives the SMS confirmation from the user, it will be sent an SMS and/or e-mail with the login credentials.

This option can be useful if you want to be sure that whoever is registering, is the actual owner of the declared number.

Editable only if user has permissions to manage the domain data.

This field is available only if the authentication mode is not set on “Click and connect. No registration, no password, “Simple password. No registration”, “PPPoE” and “OTP (One Time Password) sent via SMS.

SMS Authorization Request

If a user attempts to perform a second recording with the same mobile number, it asks for an authorization sms. It is also the case when a user already registered tries to login through a social network with a device with MAC address that differs from the one of first registration.

This field is only available if the authentication mode is not set on “Click & connect. No registration, no password, “Simple password. No registration”, “PPPoE” and “OTP (One Time Password) sent via SMS.

User Password via SMS

If enabled, the user can send an SMS text with the domain name [space] password chosen.

This field is only available if the authentication mode is not set on “Click & connect. No registration, no password, “Simple password. No registration”, “PPPoE” and “OTP (One Time Password) sent via SMS. In other types of authentication, it can be useful to enable this option to allow the user to change the password that has been assigned or to change a forgotten password.

Maximum Number of SMSs

Maximum number of SMSs that can be sent to each user during the time defined. Multiple sendings can happen if the user sends multiple registration requests on domains through automatic registration through SMS or performs many logins with the authentication method “OTP (One-Time Password) sent via SMS”.

A value equal to zero, does not limit the number of SMS that can be sent to the user.

Warning! It is recommended to define limits to prevent abuse or robot.

Send SMS Notification

If enabled, at the registration confirmation, an SMS notification will be sent to the user with the login credentials.

It is not considered in the registration through social networks.

If the authentication mode is set to “OTP (One-Time Password) sent via SMS”, the “No” value in not available.

Consider Country Calling Codes

For an automatic activation of all domain users, it considers the international calling codes defined.

Accepted Country Calling Codes

List of international country calling codes, separated by commas, accepted for automatic activation of end-users. If they are not declared, all country calling codes are available.

Visible only if “Consider International Country Calling Codes” is active.

International country calling codes must be declared in the form 00xx.

Enable Redirect

Redirect URL

Redirects the URL for users with international country county codes not accepted.

Visible only if “Consider foreign country calling codes” is active.

Propose Country Calling Codes

At the user registration, if this option is enabled, it will propose the international country calling code at system level.

If disabled, user will be required to choose an international country code.

Enable Facebook Login

URL or Page ID for “I like” or “Publish”

Define the complete URL (without HTTP://) or the Facebook page ID whichusers can click “Like” on or “Publish a post” to.

This value can be overwritten by the same field defined in gateway.

At the registration or connection using Facebook, users have the possibility to publish a post on the activity log or user’s timeline.

Possible values are:

No: users cannot publish a post;

Yes: users can publish a post to their timeline.

This value may be overwritten by the same field defined in gateway.

Warning! This feature works correctly only on HTTPS connection. It is therefore necessary to install a valid certificate in both Network Station and gateway.

If enabled and in the “ External Authentications” settings, you have configured a Twitter application, it allows users to log in through Twitter.

Define the Twitter username that the user must follow (Follower). When the user logs in, he may click “follow” before accessing the internet

This value may be overwritten by the same field defined in the gateway.

Enable Google Login

If enabled and in the “ External Authentications” settings you have configured a Google application, it allows users to log in through Google authentication.

Warning! It has been announced that, in order to improve safety, by April 2017 Google will disable its authentication services on “web views” used for the CNA. This means that it will no longer work with Google on CNA. References: https://developers.googleblog.com/2016/08/modernizing-oAuth-interactions-in-native-apps.html. We do not recommend the use of CNA, that you can disable in the data of the gateway, to authenticate with Google +.

Enable Linkedin Login

If enabled and in the “ External Authentications” settings you have configured a LinkedIn application, it allows users to log in through LinkedIn authentication.

Enable Amazon Login

If enabled and in the “ External Authentications” settings you have configured an Amazon application, it allows users to log in through Amazon authentication.

Enable VKontakte Login

If enabled and in the “ External Authentications” settings you have configured a VKontakte application, it allows users to log in through VKontakte authentication

Enable TPIN Login

If checked, it enables users to log in through the Turkish Public Identification Number.

Enable Custom OAuth Authentication

If enabled and in the “ External Authentications” settings you have configured a Custom OAuth, it allows users to log in through Custom OAuth.

Verify Email Address

In enabled, at the registration, it automatically verifies if the email address entered by the user, exists by contacting the domain’s MX server. 

Warning! In some cases, it is not possible to determine the MX server or contacting the remote mail server and therefore the check cannot be performed. In these cases the user fails to register.

Send Email Notification

If enabled, at the registration confirmation, a mail notification will be sent to the user with the login credentials.

It is not considered in the registration through social networks.

Send Email Notification to the  manager

If enabled, at the registration confirmation, a mail notification will be sent to the manager with the login credentials.

Possible options are:

• No, do not send the email to the manager.
• Yes, send the email to the manager email address.
• To specific addresses, send the email to the addresses defined in the next field.

Email Addresses

Email addresses, separated by commas, to send a confirmation email to with login credentials.

Product at the Email Validation

Product assigned at users when the email address is validated.

It can be used to motivate users to validate their email address using for example sentences like: if you confirm your email address, you will gain two hours of free internet connection.

In order to make the users validate thier email address, it is necessary to use the variable %MailValidationLink% as described in the previous “Email Notification Validation” field.

Send Email with Receipt

If enabled, the system automatically sends emails with payment receipts.

Accepted Email Domains

Restricts the registration to specified email domains separated by commas.

For example, if you want to restrict the registration only to gmail users, enter gmail.com.

Description

Redirect URLs (comma-separated)

Comma-separated list of URLs to use to redirect the user while pressing the Start Browsing button. The redirect is done randomly on one of these URLs with a Round-Robin technique.

In the URL, you can use the following variables:

%UserName%: username;

%Domain%: domain name;

%HotSpotName%: gateway name;

%MacAddress%: MAC address of the user’s device;

%OriginalAddress%: original URL;

%Gender%: sex;

%FirstName%: first name;

%LastName%: last name;

%EMailAddress%:  email address;

%Phone%: phone number;

%MobilePhone%: mobile phone;

%Address%: address;

%City%: city;

%State%: province or state;

%Country%: country;

%Zip%: Zip;

%RoomOrSite%: room or pitch number;

%DayOfBirth%: day of birth;

%MonthOfBirth%: month of birth;

%YearOfBirth%: year of birth;

%Language%: language;

%RetailersCompanyName%: reseller company name;

%ManagersCompanyName%: manager company name.

After Registration URL

Redirection URL after the user registration. 

In the URL, you can use the following variables:

%UserName%: username;

%Password%: password;

%Domain%: domain name;

%HotSpotName%: gateway name;

%MacAddress%: MAC address of the user’s device;

%OriginalAddress%: original URL;

%Gender%: sex;

%FirstName%: first name;

%LastName%: last name;

%EMailAddress%: e-mail address.

%Phone%: phone number;

%MobilePhone%: mobile number;

%Address%: address;

%City%: city;

%State%: province or state;

%Country%: nation

%Zip%: ZIP;

%RoomOrSite%: room or pitch code

%DayOfBirth%: day of birth;

%MonthOfBirth%: month of birth;

%YearOfBirth%: year of birth;

%Language%: language;

%RetailersCompanyName%: reseller company name;

%ManagersCompanyName%: manager company name.

Do not configure this option if you enable CNA. On iOS devices with CNA this option is ignored.

The redirect URL is not considered if the reidirect is enabled for international calling codes and the user registers with a international calling code that is not accepted.

Warning! Redirect after registration works only if the blocking of “popups” is not active, if you have enabled the “Show Credentials” check or if you have enabled “Display the Registration Confirmation” check.

Field

Description

Recognize the User based on the Device

Upon login, at the device’s recognition, user is not forced to enter the authentication data (username/mobile number and password).

The possible options are:

• No,
• Yes, hide the username and password fields;
• Yes, suggest and display the fields for the username and password.

Expiration of Device Recognition

Expresses the expiration time, in minutes, of the device recognition with regars to the user’s last session. A value = 0 states that there is no expiration. If the value is less than zero, it avoids suggesting the last username that has logged-in.

We recommend to enable this option if you share devices or pcs with users, like internet points, internet rooms, etc.

Switch Automatically to Registration

It automatically switches to registration for unrecognized devices/users.

Not available if the authentication mode is set to “Social login only”

Switch Automatically to Recharge

It automatically switches to recharge for devices/users recognized and expired and that have exhausted the time/traffic.

Disable Multiple Registrations

By enabling this option, the user will not be able to register multiple times from the same device. So, if the user logs in with a username and password, the device will no longer be able to make further registrations. In practice, at the first login the system matches the user to the device and no other user with different credentials can be used. This allows, for example, in the case of partially free domains, that is with a free initial time, to prevent any multiple registrations from the same device to use the free time amount of credit allowed for x times.

Not visible if the authentication mode is set to “Simple password. No registration”

Field

Description

Product

Product to enable for the domain

Free

In enabled, the product is free and the user is not forced to purchase.

If disabled, the price field will be displayed.

Display with Standard Registration

If enabled, the product will be selectable during standard registration.

Display with Social Registration

If enabled, the product will be selectable only with registration through social network.

Display at the Recharge

If enabled, the product will be available only if the user is processing a recharge.

Printing Group

By assigning a group code common with other products, in printer, it displays the choice of the group and then the list of products associated with it. In case there are many products in the domain, grouping will help the operator during the selection phase.

Enable Printing Card

If enabled, the product will be available for printing the “Cards” using the thermal printer combinable with the “Network Station Printer“.

• Visible only if the authentication method is set on “With registration by the user”, “With registration by the user without password” or “With registration by the operator”.

Enable Printing Voucher

If enabled, the product will be available for printing the “Vouchers” using the thermal printer combinable with the “Network Station Printer“

Field

Description

Assign the Free Product

It assigns the first free product at the registration without displaying the list of products.
The available options are:

• Yes: (it assigns the free product);
• No (it never assigns automatically the free product and user can choose the product from the list. In this way user can choose between more free or paid products and he will be informed on the product characteristics that will be assigned him).

• Not visible if the authentication mode is set to “PPPoE”

Reassign the Free Product

If you have defined only one free product (with time/traffic free or without price), it reassigns automatically the free product. 
If you have defined more free products and the authentication mode is set to “PPPoE”, the first free product is assigned. With the other authentication mode, if you have defined more free products, the automatic assignment is not executed. The procedure will ask the user to choose the paid or free product.
The possible options are:

• Never. It never reassigns the free product
• At Expiration or Exhaustion. The product is reassigned if user exhausts the credit or if the product expires;
• At Expiration. The product is reassigned only at the expiration of the product.
• At Expiration or Exhaustion with a Charged Product. The product is reassigned only if the user has a paid product out of time and/or traffic and/or expires;
• At Expiration with a Charged Product. The product is reassigned only if the user has an Expired paid product

• If you have enabled the “reassign the free product at the expiration” option, also the re-registration is enabled. In practice, if an expired user tries to registrate with his username or mobile phone, the system does not display any alert error message and it allows to continue as if it was the first registration, although in reality the user will be the same.

Code Type for Vouchers

It defines the type of code to print for the “Vouchers
The possible options define the format of the voucher you want to use.

Warning! If you change this parameter the previously created vouchers are no longer usable.

Field

Description

Alternative Language

Alternative language to be displayed to users when the browser language is not recognized or is not active.
It is also used for notifications sent through sms and/or e-mail to users who register on domains with authentication mode “With sending SMS from the user”

Enable English Language

If enabled, allows users to view the login page in English.

Enable Spanish Language

If enabled, allows users to view the login page in Spanish.

Enable French Language

If enabled, allows users to view the login page in French.

Enable Italian Language

If enabled, allows users to view the login page in Italian.

Enable German language

If enabled, allows users to view the login page in German.

Enable the First Additional Language

If enabled, allows users to view the first additional language defined in “General Options” (this option is only available for the administrator of the system).

In case of the Enterprise Edition, you can allow users to view the first additional language defined in the domain or in the gateway.

Enable the Second Additional Language

If enabled, allows users to view the second additional language defined in “General Options” (this option is only available for the administrator of the system).
In case of the Enterprise Edition, you can allow users to view the first additional language defined in the domain or in the gateway.

Enable the Third Additional Language

If enabled, allows users to view the second additional language defined in “General Options” (this option is only available for the administrator of the system).

In case of the Enterprise Edition, you can allow users to view the first additional language defined in the domain or in the gateway.

Field

Description

MailChimp Audience ID

To enable synchronization of the domain’s users, enter the “MailChimp Audience ID”.

To complete the activation of the synchronization, you need to enter the MailChimp API Key in manager data.

Export Type

Type of export to MailChimp.

You can select one of the following values:

• Disabled: the export is not active.
• Only users with consent to newsletter: export only users who have given consent to newsletter.
• Only users with marketing consent: exports only users who have given consent to marketing.
• Only users with consent to newsletter and marketing: export only users who have given both consent to newsletter and marketing.
• All users: export all users.

In all cases, you can export only for users who have an email address

Field

Description

Consider Users Disconnected After

It considers automatically logged off users with a connection active for more that the days you have defined. In some case, gateways may not send the users’ disconnection, and therefore the system would consider them as still activective. In other words, if you active this option, the system automatically closes user connections established for a longer time than the days you indicated.

If a user is considered disconnected based on the indicated value, in the “User connection Log”, “Forced Closure 1” is reported in the disconnection cause.

This option is not considered on gateways that have enabled the “Force Disconnections” option.

Notes for the Domain

Enter possible notes for the domain.

Available only if the user has permissions to manage the domain data.

Domain Locked

If enabled, it blocks all the access by all users in the domain.

Available only if the user has permissions to manage the domain data.