Inside the admin panel¶
The admin panel (web panel) is ControlAI's main and only interface for the university. Everything the system computes and collects lives here: class-session reports, metrics, ratings, lesson observation forms, the schedule. Results never need to be exported anywhere — university staff log into the panel and see what's relevant to their role: the rector's office sees the university-wide picture, a dean sees their own faculty, an instructor sees only their own class sessions.
How the panel is organized¶
- Login-based access. Every staff member has their own account and their own role.
- Everyone sees only their own. Access is scoped by role and by university (and, where relevant, by faculty): an instructor sees their own class sessions, the rector's office sees the whole university, a dean sees their own faculty, and so on.
- Two interface languages — Uzbek and Russian.
- Works in the browser, on both computer and phone.
What the panel is made of¶
Sections are grouped by meaning (section names are the product's own terms; the parenthetical text shows what this means at a university):
| Group | Sections |
|---|---|
| Analytics | Dashboard · Lessons (class sessions) · Teachers (instructors) · Coaching · Attrition risk (student-body risk) · Branches (faculties) · Analysis |
| Management | Schedule (class-session grid) · People & Groups · Courses (disciplines and degree programs) · Classrooms & Equipment (auditoriums) · Consents |
| Operations | Operations · Billing · Payroll (workload accounting) |
| Personal | My Profile (for instructors) |
What each of these screens shows, and what the reports look like, is in the chapter «Sample Results».
Roles: who is who¶
Role names in the panel are ControlAI's product terms. At the university, each role is held by a specific position — the mapping is in the table below:
| Role in the panel | Who this is at the university | Guide |
|---|---|---|
| Owner | the rector's office — the rector or the vice-rector for academic affairs, the system's client | owner.md |
| Branch Manager | the dean (dean's office) — the faculty's operational manager | branch-manager.md |
| Academic Manager | the quality-control office (ichki ta'lim sifati nazorati bo'limi) or the head of department — reviews the AI's verdicts against the observation form | academic-manager.md |
| Lead Teacher | the head of department (kafedra mudiri) — teaches and sees their own department | lead-teacher.md |
| Teacher | an instructor — sees only their own | teacher.md |
| Mentor | mentor of junior instructors | mentor.md |
| Superadmin | the ControlAI team (us), operating the platform | superadmin.md |
Implementation status. The current admin-panel MVP has three roles set up — owner (rector's office), manager, and teacher (instructor). The full role model (separate dean, quality-control office, head of department, mentor) rolls out as the product grows: for now, "dean" and "quality-control office" are merged into a single manager role. The guides below describe the target access picture for each role.
Who doesn't log into the admin panel¶
- Students — do not log into the panel: the system analyzes the class session as a process and the instructor's work, not individual students, so there are no personal accounts or profiles for students (see «Boundaries»).
Key takeaway from this chapter: the admin panel is the product's single web hub, where everyone, under their own role, sees only their own: the rector's office sees the whole university, a dean sees a faculty, an instructor sees their own class sessions. Below is a separate guide for each role: what it sees and what it can do.
→ Next: we go through the roles one by one, starting with the rector's office. See the full picture of results in «Sample Results».