Build the admin surfaces: web admin and Telegram operations #12

Open
opened 2026-03-10 14:40:55 +03:00 by sirily · 0 comments
Owner

Problem
The repository still lacks the promised admin surfaces for users, subscriptions, invoices, generations, provider keys, proxies, and operational alerts.

Why this matters
Key-pool management, billing operations, and incident handling are central to the product, but today only Telegram pairing and one invoice admin endpoint exist.

Acceptance criteria

  • Implement the web admin surface for the core operational entities.
  • Extend the Telegram bot with authenticated admin commands and alerts.
  • Preserve the pairing rule that approval can only complete through the server-side CLI.
  • Ensure all state-changing admin operations are auditable.
Problem The repository still lacks the promised admin surfaces for users, subscriptions, invoices, generations, provider keys, proxies, and operational alerts. Why this matters Key-pool management, billing operations, and incident handling are central to the product, but today only Telegram pairing and one invoice admin endpoint exist. Acceptance criteria - Implement the web admin surface for the core operational entities. - Extend the Telegram bot with authenticated admin commands and alerts. - Preserve the pairing rule that approval can only complete through the server-side CLI. - Ensure all state-changing admin operations are auditable.
sirily changed title from Build the MVP admin surfaces: web admin and Telegram operations to Build the admin surfaces: web admin and Telegram operations 2026-03-10 14:56:20 +03:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sirily/nroxy#12