1.9 KiB
1.9 KiB
CHANGELOG — Forefront Wireless Operations Portal
2026-07-25 (PM) — Dual Access & Device Management Scoped
Major Design Decisions
Dual-access portal — same domain, different views:
/staff/*— role-gated (Admin, Tech, View Only)/customer/*— tied to Splynx customer record
Three staff roles:
| Role | Permissions |
|---|---|
| Admin | Full CRUD — devices, billing, templates, users |
| Tech | Troubleshoot, view all equipment, reboot CPEs — no billing |
| View Only | Read-only dashboards |
Staff dashboard = 6 device sections:
- MikroTik routers (5 × CCR2004) — status, CPU, throughput
- Ubiquiti backhauls — point-to-point link signal/capacity
- Customer CPEs — subscriber device health, reboot action
- MikroTik switches — port map, PoE budget
- Algcom PDUs & UPSs — SNMP-polled outlet/battery status
- TPDIN Web Monitor 3s — environmental (temp/humidity/contacts)
Device inventory with auto-SNMP templates:
- Staff add devices with make, model, IP, SNMP community, web URL
- Backend probes SNMP for unknown make/model combos
- Maps discovered OIDs → widget suggestions
- Staff approves → reusable template saved
- Any new device with same make/model inherits template automatically
Customer side:
- Account/billing management
- Current package view
- Marketplace — browse upgrade plans, compare, request change
Portal auth separate from Splynx — Splynx is billing source-of-truth; the portal runs its own user table with roles. Customer accounts are linked to Splynx customer IDs.
2026-07-25 (AM) — 4-Source Architecture
Multi-source aggregation architecture: Splynx (billing/CRM), UISP (network management), MikroTik (router telemetry), Zabbix/SNMP (infrastructure monitoring). Build phases 1-4 defined. Zabbix migration options documented.
See earlier CHANGELOG entry for Splynx API reconnaissance details.