Skip to main content

​
Configure the ISP workspace

Account-wide settings are reserved for the operator administrator. Staff, agents, and affiliates normally manage only their own profile and sign-in security. Settings shown in the UI remain subject to route authorization and ISP account capabilities.

​
Settings map

​
Branding

Open Settings → Branding to configure the identity shared across the operator panel, subscriber portal, emails, and captive portal.

​
Important behavior

  • Saving Country also updates the billing currency and workspace timezone shown by the form.
  • Support email is verified by a six-digit code before it becomes the public contact.
  • Enabling Terms & Conditions requires non-empty terms content.
  • The rich-text terms field sanitizes scripts and unsafe HTML when saved.
  • Removing or replacing a logo changes subscriber-facing surfaces; verify the portal after saving.

​
Domain

The domain page manages the workspace URL. The custom subdomain field is required when starting a switch. Before confirming a production change:
  1. Notify staff and subscribers who use saved links.
  2. Record integrations that call the old hostname.
  3. Complete the confirmation workflow.
  4. Test sign-in, captive pages, customer portal, router downloads, payment callbacks, and webhooks.
Do not assume that a domain switch updates external provider dashboards or DNS you control outside Centipid Billing.

​
PPPoE lifecycle

Use Settings → PPPoE to control:
  • pruning of inactive subscriber records;
  • pre-expiry reminder behavior;
  • fair-usage-policy alerts;
  • automatic invoice behavior;
  • invoice number prefix.
Changes affect automated processing. Review message templates and a representative subscriber before enabling reminders or invoice generation for the whole subscriber base.

​
Hotspot and captive portal

Use Settings → Hotspot to select a portal template, upload a background, set the post-purchase redirect, arrange portal sections, control inactive pruning, choose a username prefix, set unused-voucher expiry, and provide manual purchase instructions. The redirect field should point to a valid destination intended for customers. Test it from an actual captive flow; a normal browser session does not reproduce every captive-network restriction. See Captive portal.

​
Payments

Use Settings → Payments to choose a gateway, complete the required credential fields, and switch from the current gateway. Sensitive changes may require an OTP and a readiness confirmation. Follow Payment gateways instead of copying credentials from another ISP account.

​
Communication providers

The SMS and WhatsApp pages open channel-specific provider marketplaces. Email opens a single SMTP configuration form rather than a provider list. Configure only services for which the ISP has valid commercial access and credentials. After saving:
  1. send a controlled message;
  2. confirm the provider accepted it;
  3. inspect delivery state where available;
  4. verify sender identity and reply behavior;
  5. then enable automated templates.

​
Message templates

Templates can control:
  • PPPoE renewal confirmation;
  • Hotspot purchase confirmation and new-users-only behavior;
  • voucher delivery;
  • PPPoE and Hotspot expiry notices;
  • PPPoE pre-expiry reminders;
  • bundle-usage warnings and their trigger percentage.
Template variables are inserted from the UI. Do not invent variable names: unsupported placeholders may be delivered literally. Keep SMS length in mind; message fields enforce a 320-character maximum.

​
Loyalty points

When enabled, the loyalty program awards points when configured payment thresholds are crossed and allows redemption subject to a minimum balance and value-per-point rule. Before enabling it, model a normal payment and redemption so the commercial value is intentional.

​
Operator alerts and outage compensation

Router alerts can be sent to specified phone numbers or, when the list is empty, the administrator audience defined by the application. WhatsApp can be preferred when a gateway is configured. Outage compensation can credit a percentage of qualifying downtime, filtered by minimum duration, connection type, and package. It can optionally notify affected subscribers. Review the percentage, qualifying packages, and notification copy carefully because this setting can change subscriber expiry/credit state at scale.

​
AI Assistant

Select the supported AI provider and optionally store your own API key. If the key is blank, the application can use the platform default when available. API keys are secrets: do not paste them into messages, screenshots, or webhook payloads.

​
Developer settings

​
API tokens

Token name is required. Create a narrowly named token for one integration, copy the plaintext value when shown, and store it in a secret manager. Revoke tokens that are unused, exposed, or associated with former staff.

​
Webhooks

A webhook requires a label, valid HTTPS URL, and selected events. A signing secret is generated when left blank. Verify signatures in the receiver, make processing idempotent, return quickly, and monitor failed deliveries. Pausing a webhook is safer than deleting it during a temporary incident.

​
Safe change procedure

For settings that affect money, access, bulk messaging, domains, or automated credits:
  1. record the current value;
  2. identify affected subscribers and integrations;
  3. make one coherent change;
  4. save and verify the success response;
  5. test with a controlled account/device/transaction;
  6. review logs or visible status;
  7. roll back promptly if the expected result does not occur.