App Settings
Configure group-wide customer, billing, notification, Hotspot, privacy, and automation policies
Settings → App Settings contains group-wide policies. A Group Admin's choices apply to the operators, sub-operators, and customers belonging to that group.
Select the required values and click Save App Settings. Changes to customer-facing permissions and notification routing take effect immediately. Network authentication changes are synchronized with RADIUS automatically.
Customer and reseller controls
| Setting | Effect when enabled |
|---|---|
| Remove customer from MikroTik when deleted | Removes matching PPP and Hotspot records from the assigned router as part of customer deletion. |
| Delete customers inactive for six months | The daily cleanup archives eligible suspended or disabled customers after six inactive months. |
| Customers can buy internet time in minutes | Adds a minute-purchase form to the customer portal and charges a prorated amount from wallet balance. |
| Customers can edit profile | Allows access to the customer profile-edit workflow. |
| Resellers can create without recharge | Lets operators and sub-operators create an account without creating its initial recharge/payment. |
| Resellers can downgrade packages | Lets operators and sub-operators move customers to a lower-priced package. |
| Customers can recharge online | Shows customer recharge and package-purchase actions and accepts their requests. |
| Operators can add advance wallet balance | Allows non-group-admin operators to add customer advance balance. |
| Show complaints from operators and sub-operators | Includes descendant operators' customer complaints in the Group Admin complaint view. |
| Hide mobile number in customer lists | Masks subscriber mobile numbers in desktop and mobile customer lists. |
The six-month cleanup and MikroTik removal options perform real lifecycle actions. Review archived-customer and router backups before enabling them.
Billing and suspension
| Setting | Effect |
|---|---|
| Generate monthly bills for suspended customers | Includes suspended monthly customers in bill generation. |
| Generate monthly bills for disabled customers | Includes disabled monthly customers in bill generation. |
| Daily PPPoE billing cutoff time | Defines the time of day after which an expired daily PPPoE account is eligible for suspension. |
| Suspension hour for overdue customers | Sets the group-local hour used by automatic overdue suspension. |
| Emergency balance limit | Allows minute purchases to take a wallet below zero up to this configured amount. Set 0 to disallow negative balance. |
| Internet before online payment | Applies the selected package before the payment provider confirms payment. Leave disabled when payment confirmation must occur first. |
Notifications
Choose a Default notification channel and a Fallback notification channel from SMS and WhatsApp. Manual messages, supported OTP flows, and system notifications try the default channel first. If delivery cannot be completed, ISPBills retries through the fallback channel.
The two channels should normally be different. Configure and test both gateways before relying on fallback delivery. SMS and WhatsApp attempts appear together in SMS & Notifications → Message History.
Registration, identity, and MAC policy
| Setting | Effect when enabled or selected |
|---|---|
| Hotspot mobile must be verified | Requires OTP verification during Hotspot self-registration. |
| Grant access immediately after registration | Activates the new account and logs it into Hotspot after successful registration. When disabled, the account starts suspended. |
| Identity verification method | Uses Mobile OTP, National ID, or Manual Review for new self-service registration. |
| Allow randomized MAC addresses | Accepts locally administered/private device MAC addresses on the captive portal. |
| Auto-bind new Hotspot account MAC | Binds the registration device to a newly created Hotspot account. |
| Auto-bind MAC after recharge-card payment | Binds the recorded device MAC when a recharge-card payment activates service. |
Allow PPPoE customers to use Hotspot
Enable Allow PPPoE customers to connect to Hotspot too when broadband customers should also receive WiFi-zone access.
The customer enters their registered mobile number in the existing Hotspot captive-portal form. ISPBills finds the PPPoE account within the same group and authenticates the Hotspot session with its existing PPP credentials. The device MAC is session context only: it does not replace the PPP username, assigned router, or saved PPP MAC.
The policy permits:
- one active PPPoE session; and
- one active Hotspot session for the same customer.
A second session of either service is rejected. PPP-only IP/profile attributes are not applied to the Hotspot session. Existing Hotspot customers continue using normal MAC-based authentication without any change.
Maps
Save the group's Google Maps API key to enable map and geocoding features for that group. In Google Cloud, enable the Maps JavaScript API and Geocoding API and restrict the key to the ISPBills domain.
Recommended rollout
- Configure and test SMS and WhatsApp gateways.
- Save notification default and fallback channels.
- Review registration, MAC, and customer self-service options.
- Enable billing or destructive lifecycle automation only after confirming the intended group policy.
- If enabling PPPoE-on-Hotspot, test with one active PPPoE customer using their registered mobile number, then confirm one session of each type appears in Online Customers.