Skip to main content

Config

Overview

Config is where you set up how your site behaves — your business identity, billing rules, how customers are verified, how messages and payments work, and the integrations that connect the platform to your other systems. You usually set these once when you go live, then revisit them when something about your business changes.

SettingWhat it controls
SiteYour business identity, region/currency/timezone, subscriber defaults and the public customer website.
BillingBilling cycle and grace rules, invoice numbering and templates, tax registration, bank details, and reusable billing profiles & taxes.
KYCHow customer identity verification (KYC / eKYC) works and which documents are required.
NotificationsThe Mail, SMS, WhatsApp, Telegram and Push channels used to message customers, plus alert timing.
Payment GatewaysThe online payment gateways customers use to pay and recharge.
Subscriber PortalWhich features your customers can use in their self-service portal/app.
IntegrationsCATV OLT, ACS (TR-069), Tally, OTT, IPTV and LQoS integrations.

Each page is permission-gated, so you'll only see the settings your role allows. Some depend on your business model or add-on modules and won't appear otherwise.

How the settings pages work

  • Save — most pages have an Update (or Save) button at the top and/or bottom; some are split into tabs or accordion panels, each saved separately. Changes take effect immediately and are recorded in the audit log.
  • "Apply To All Subscribers" — several defaults (billing day, grace period, expiry time…) have this checkbox. Ticking it doesn't just set the default for new customers — it overwrites that setting on every existing subscriber. Use it deliberately.
  • Multi-site accounts — if your account manages several sites, some pages add a Copy to / Allowed Sites selector so one configuration can be pushed to several sites at once. Single-site operators just configure their own site.

:::caution These pages hold credentials Many Config pages store secrets — API keys, payment-gateway keys, SMTP passwords, bot tokens. Treat them like passwords: don't share your screen or screenshots showing these fields, and only regenerate a key when you're ready to update wherever that key is used. (In this documentation every such value has been hidden.) :::