Docs
The subscriber portal
Where your subscribers sign in, what they can do there, how the session recognises them without a password, and how the portal carries your branding.
Every tenant gets a subscriber portal on its own address. It is a progressive web app: a subscriber can install it from the browser and it then behaves like an application on the phone.
Where subscribers open it
The portal lives under /user/ on your tenant's address. Give your subscribers
that link, not the instance's home page — the instance address resolves no
tenant and will show them a sign-in screen for an account they do not have.
Signing in without typing anything
A subscriber connected through one of your routers can be recognised from the session itself, without a username or password. The router rewrites requests for a fixed address to the portal, and the instance matches the request back to the live session on that router.
This works behind carrier-grade NAT, where several subscribers share one public address, because the match is made against the router's own session table rather than against the public address alone. If the subscriber has no live session, they get the ordinary sign-in form.
Branding and designs
The portal carries your logo, your colours and your name, per tenant. There are five designs to choose between; they differ in layout and density rather than in what they offer, so picking one is a matter of which suits your customers.
What a subscriber can do
- See the plan, the remaining quota and the expiry date.
- Top up a wallet and pay online, where you have a gateway configured.
- Redeem a card.
- Read their own session history and usage.
- Pause the connection or filter it behind a PIN, for a household.
- Open a support ticket and follow it.
Telegram and WhatsApp
The same account can be reached from a Telegram bot, which offers the same operations as the portal for the subscribers who prefer a chat window. WhatsApp is available as a notification channel and as a support intake path.
If it did not work
- The subscriber sees a sign-in screen instead of being recognised. They have no live session on a router the instance manages, or they are reaching the portal over mobile data rather than through your network.
- The portal shows the wrong branding. Branding is resolved from the host, so check they are on your tenant's address and not on the instance's.
- Installing the app does nothing. The install prompt is the browser's, and it appears only over HTTPS on a host the browser has seen more than once.
Last updated