Documentation

Operator guides

Short, practical guides for running your hotspot on AetherNet. Each one mirrors what actually happens in the console — no imaginary buttons.

Getting started

Pilot operators are onboarded personally. Once your workspace exists, this is the shape of day one.

1.Request access from the contact page — tell us about your routers and how you sell today.
2.We create your workspace and walk you through a short demo with your own numbers.
3.Sign in, invite your staff (Staff → New staff account), and set up two-factor for admins.
4.Create your packages and speed profiles under Packages.

Enrollment is router-initiated: nothing on your network listens for the internet, and the token is single-use.

1.Open Routers → Register router and fill in the name, site and purpose.
2.Copy the generated bootstrap command — it contains a one-time token, valid briefly.
3.Paste it into the RouterOS terminal. The router fetches the installer and checks in.
4.The console shows the router as enrolled only after it has been verified — then choose a provisioning plan.
5.Apply the plan from the router page: preview the change, confirm, and read back the result.

Two ways to sell: printed batches for resellers, or single codes at the counter. Both record the full trail.

1.Create a package (time, data or both) — validity runs from first activation.
2.For resellers: Vouchers → New batch, generate, export/print and hand out.
3.At the counter: New sale picks a package and (optionally) a customer, then prints the code and receipt.
4.Unused codes can be voided from Sales; they return to stock and the void stays in the ledger.

Your team works tickets with real SLA clocks; the network raises incidents on its own.

1.Support Hub → Tickets: create or triage, assign, reply, and resolve with a note.
2.Run diagnostics from a ticket to check a voucher’s stored facts in one click.
3.Incidents open automatically when a router goes silent, and resolve when it returns.
4.Write down what worked: Knowledge Base articles and playbooks are one click from a ticket.

Roles carry permissions; people carry roles. Nothing is granted by knowing a URL.

1.Staff → New staff account: identity, role and a first-login password change.
2.Roles give exactly what the job needs — eleven built-in roles or a custom one.
3.Admins should enable two-factor under Security after their first sign-in.
4.If someone leaves: Manage → Suspended, then revoke their devices in one click.

The ledger is your source of truth — prices, receipts, voids and exports.

1.Every sale keeps a price and currency snapshot — UGX-first and multi-currency ready.
2.Receipts print for counter sales; batches export as CSV for resellers.
3.Analytics → Reports exports the numbers you need for bookkeeping.
4.Mobile-money payments are on the roadmap with verified, reconciled callbacks — until then, cash rules apply.

Stuck on something? Use the contact page — pilot operators get a direct line to the team, and the answer usually becomes a new guide.

Request access and we’ll set up your workspace and first router together.