What a TiLive Recorder Admin Panel Should Control
A recorder backoffice is not a dashboard decoration. It has to let the operator act: change plans, ban users, open tickets, inspect recordings, and see whether the recorder is healthy.
User controls must write to the database
Plan changes and ban states should not be mock buttons. They need server-side routes and persistent database fields.
That way the admin panel reflects the same state the bot and public site can use.
Tickets need status and notes
Support tickets should be creatable from the admin, tied to a Telegram user, and moved between open, waiting, and closed.
Internal notes help track what happened without scattering support context across chats.
Recorder views should stay operational
Active recordings, logs, watchlist cycles, CDN health, and system metrics are for daily operations.
They should be dense, predictable, and tied to real data as the backend matures.
Use the admin panel to change user state and support tickets from one place before scaling traffic.
Open @tiliverec_bot