Inside the admin panel¶
The admin panel (web panel) is the main and only interface of ControlAI for a center. Everything the system has computed and collected lives here: reports, metrics, ratings, methodology, schedule, billing. Results don't need to be exported anywhere — the center's staff log into the panel and view whatever pertains to their role.
How the panel is organized¶
- Login with credentials. Each staff member has their own account and their own role.
- Everyone sees only their own data. Access is limited by role and center (and, where needed, by branch): a teacher sees their own lessons, the owner sees the whole center, and so on.
- Two interface languages — Uzbek and Russian.
- Runs in the browser on both desktop and phone.
What the panel consists of¶
The sections are grouped by purpose:
| Group | Sections |
|---|---|
| Analytics | Dashboard · Lessons · Teachers · Coaching · Churn risk · Branches · Analysis |
| Management | Schedule · People and groups · Courses · Rooms and equipment · Consents |
| Operations | Operations · Billing · Payroll |
| Personal | My profile (for the teacher) |
What each of these screens shows and what the reports look like is covered in the “Result examples” chapter.
Roles: who's who¶
| Role | Who this is | Instructions |
|---|---|---|
| Owner | director/owner of the center — the paying client | owner.md |
| Branch manager | operational manager of a single branch | branch-manager.md |
| Academic manager (methodist) | quality supervisor, reviews the AI's verdicts against the methodology | academic-manager.md |
| Lead teacher | teaches and mentors junior staff | lead-teacher.md |
| Teacher | teacher, sees only their own data | teacher.md |
| Mentor | runs supplementary/special lessons | mentor.md |
| Superadmin | the ControlAI team (us), platform operations | superadmin.md |
Implementation status. In the current admin-panel MVP, three roles are set up — owner, manager, and teacher. The full role model (separate branch manager, academic manager, lead teacher, mentor) is rolled out as the product grows: for now the branch manager and academic manager are merged into a single “manager” role. The pages below describe the target picture of access for each role.
Who doesn't access the admin panel yet¶
- Parents — they don't have a panel yet. Their channel (a brief report on their child) is future work, a separate portal or app (see “Roadmap”).
- Students — they don't access the panel today, but they will get their own profile (on the roadmap): personal progress, participation in lessons, week-over-week trends. More details are in the “Roadmap”.
Key takeaway from this chapter: the admin panel is the single web hub of the product, where everyone, under their own role, sees only their own data. Below are separate instructions for each role: what it sees and what it can do.
→ Next: we'll go through the roles one by one, starting with the owner. For the full picture of results, see “Result examples”.