
Parameter Name | Description | |
Guest Wi-Fi Name | Required | Set the wireless network name for external broadcasting, such as Guest-Wi-Fi or Visitor-Net. |
Employee Application / Guest Access Authentication Permission | Control which internal employees are authorized to initiate guest network access requests or participate in the authentication process. | All members: All employees can apply for guest accounts (suitable for open organizations). Selected members: Only specified departments/roles can apply (such as Administration, HR, and Project Manager), reducing the risk of misuse. |
Guest Authentication Protocol Type (Effective for All Routers) | Determines the underlying authentication technology stack and affects compatibility and security. | Portal authentication: Web pop-up login that supports multiple methods such as SMS/QR code scanning/username-password, with strong compatibility. |
Guest Authentication Method | Provides three mainstream authentication paths, and administrators can use one or multiple paths in combination. | Account and password: Guests manually enter their account + password to log in, and the system can optionally send an SMS notification. QR code authentication: After an employee submits an application, a QR code is generated. Guests can scan it with their phones to connect to the network with one tap. SMS self-service authentication: Guests receive a verification code on their mobile phones and register a temporary account on their own. The account is valid for 24 hours and must be re-applied for upon expiration. |
Guest Account Password Notification Method | Determines how to deliver login credentials to visitors. | SMS notification: The system automatically sends an SMS message to the guest's mobile number, including the account credentials or a link. Applicant self-notification: The applying employee notifies the guest verbally/WeChat/email. This method is highly flexible but disperses responsibility. |
Collect Visitor Information | Controls whether visitor basic information is mandatorily collected during application for audit and traceability purposes. | After this feature is enabled, you can select guest phone number, visit time, and visit reason. Multiple selections are supported. After selection, when a guest connects to Wi-Fi, iOA collects the guest information and displays it on the application records page for guest network access. |
Guest Account Password and SMS Self-Service Authentication with Inviter Information Verification | Anti-spoofing mechanism | After this feature is enabled, visitors are required to fill in the inviter information (any of name/employee ID/phone number/email) when applying, and the system will verify whether the employee exists and has the required permissions. |
Validity Period | Calculated from 00:00 on the visit date | Set a default lifecycle for guest accounts. Accounts automatically expire upon timeout. Calculation logic: The countdown starts at 00:00 on the visit date, not from the application time. Example: If the application is submitted on 2025-01-30 and the visit date is 2025-02-01, the validity period starts at 00:00 on February 1. |
Limit on Concurrent Terminal Connections | Controls the maximum number of devices allowed online per visitor account to prevent account sharing or malicious occupancy. | No restriction: The same account can log in on multiple devices simultaneously, which poses a security risk. 1–4 devices: Set a limit. For example, 1 device = one account per person, and 2 devices = tablet + phone. |






Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan