Culmen Staff Panel

A web panel your support staff can actually use, without giving them router access.

What staff can do

• Add, block and unblock subscribers; edit name, address, phone and expiry
• Change plan from the subscriber row — every sellable plan grouped by tier; the new profile is applied and the session reconnected in one step. Moves a panel cannot make safely — a one-off plan, a hand-pinned customer, a move between routers — are refused rather than half-applied
• Reset quota — clears usage, removes the throttle and forces a reconnect, in one action
• Release throttle for a temporary lift; reset MAC binding when a customer changes router
• Disconnect a session via CoA, without touching the router
• Live speed gauge — read a subscriber's actual throughput from the panel
• Connection history — every session start and stop, so "my internet was down" becomes a question of fact
• Remote web — one click to the subscriber's own router, from their live session address
• Generate router secrets as an idempotent .rsc file — one import instead of per-customer paste
• Export to Excel — real .xlsx, no encoding problems

Finding things

• Provider column, filters and pagination across the subscriber list, plus a show-all view
• Two search boxes — name (Arabic or English) or phone on one side, username on the other
• Card logos rendered inline; dashboard boxes for the numbers you check first
• Renewal tiles for your own servers and subscriptions, with dates editable in place
• Roughly 24× faster than the first build — the collation was the bottleneck, not the queries

Finance

• Saved months with append-only edits — corrections are recorded, never overwritten
• Four export formats

Why it matters

The common failure is a panel where "reset quota" only does part of the job — the customer sees 0 GB used but stays throttled, and calls back angry. Each action here performs every step it needs to, in the right order, including the reconnect.

The numbers staff see are the numbers the system enforces: usage comes from the quota engine's own meter, and expiry turns red the minute authentication starts rejecting — not hours later because of a timezone mismatch.

Role-based logins with bcrypt password hashing.