For schools rather than solo teachers, the Admin Dashboard is where a school owner or coordinator runs the account: sending time-limited teacher invites, assigning each teacher's classes and subjects, uploading a school logo for branded PDF output, and managing the plan and billing.
It's scoped to a single school by design — a school_admin sees and manages their own school's teachers and settings, nothing across other schools.
Every teacher invited through the dashboard lands in the same Lesson Planner, Worksheet Builder, and Quiz & Assessment modules described above, just under the classes and subjects their admin assigned them.
How it works
- Invite teachers. Send a single-use, 7-day invite link by role — teacher or school admin.
- Assign classes & subjects. Set what each teacher is responsible for, so their content generators are pre-scoped correctly.
- Brand and manage. Upload a school logo for PDF branding, and manage the plan tier and billing from the same dashboard.
Why it works for teachers — HEART
Google's HEART framework (Happiness, Engagement, Adoption, Retention, Task success) is a standard way to evaluate whether a product actually helps the people using it, not just whether it works technically.
- Happiness
- For a school owner, manually onboarding each teacher and explaining what to fill in is overhead they'd rather not repeat every time staff changes — an invite link removes that step.
- Engagement
- Because assignments are set centrally, a newly invited teacher opens Muallim already scoped to their actual classes, not staring at empty dropdowns.
- Adoption
- The same account creation flow used for a solo teacher extends naturally to a school — no separate product to learn, just an admin layer on top.
- Retention
- Billing, teacher-seat limits, and branding live in one dashboard a school admin returns to monthly, not scattered across support emails.
- Task success
- Invites are single-use and expire after 7 days by design, so an admin isn't left guessing whether a link was already used or is still valid.
Why you can trust it — E-E-A-T
Experience, Expertise, Authoritativeness, and Trustworthiness — Google's framework for content quality, applied here to how this feature was actually built and who stands behind it.
- Experience
- Teacher-seat caps and the invite/assignment flow are modelled on how a small Pakistani school actually staffs a term — a handful of teachers, each covering specific classes and subjects, not an open-ended enterprise org chart.
- Expertise
- Permissions are role-scoped in the underlying system, not just hidden in the UI — a teacher account genuinely cannot reach another school's data, and a school_admin genuinely cannot reach another school's dashboard.
- Authoritativeness
- Billing and plan management are handled directly by DIGIT Pakistan, the same team that built and operates every other module on this page.
- Trustworthiness
- An admin's write actions are blocked with a clear message rather than silently allowed if a school's plan lapses — payment status is enforced consistently, not just displayed.
FAQ
How many teachers can a school invite?
It depends on plan tier — School Starter and School Pro carry different teacher-seat caps. See Pricing for current limits.
What happens if a teacher invite isn't used?
Invite links expire automatically after 7 days and can only be used once.
Can a teacher see other teachers' content?
No — each teacher's generated content is their own. The admin dashboard manages accounts and assignments, not other teachers' generated material.
From the Journal
More on why School Admin Dashboard works the way it does: What's live in the beta and Built for teachers, by teachers.
Ready to try School Admin Dashboard? Get started free or see every feature.