Attova Admin Dashboard
Admin view: enrol students, schedule classes, track sessions and revenue for a tuition centre
Overview
Attova is a company product for Australian tuition centres. Each centre runs as an isolated organisation: onboarding, people, classes, sessions, attendance, family invoices, and payments. The core loop is mark attendance, approve when needed, draft GST-aware invoices, issue them, and record payment. Platform operators manage tenants and plans from a superadmin layer. this case study covers the product and the engineering I led.
- Role
- Senior software developer (Tech lead)
- Team
- Developer team (company product)
- Timeline
- Company product · ongoing
- My contribution
- Tech lead on a commercial multi-tenant SaaS: organisation tenancy, permission matrix, attendance-to-GST-invoice pipeline, Stripe subscription plan enforcement, and portal routing for superadmin, owner/admin, teacher, parent, and student.
Problem
Centres were stitching enrolment, attendance, and invoicing across spreadsheets and chat. A shared SaaS had to keep tenant data isolated, charge GST correctly when registered, and give each role a portal that matched real centre work.
- True multi-tenant isolation for many centres on one codebase
- Attendance that becomes family or adult-learner invoices without re-typing
- Separate experiences for platform ops, centre staff, teachers, parents, and students
What Attova does
A centre completes onboarding, adds instructors and families, creates classes with schedule and rate, then runs the week from sessions. Teachers mark attendance. Admins approve unless auto-approve is on. Draft invoices appear for the family billing cycle; admins issue them and record payment. Parents only see issued invoices for their children.
- Organisation workspaces with AU defaults (timezone, AUD, ABN, GST flags)
- Students, parents/families, and instructors with enrolment into classes
- Recurring class schedules, generated sessions, and extend-schedule flows
- Attendance submit → approve → draft invoice → issue → payment
- SaaS subscription plans and limits enforced per organisation
Who uses it
Access is a permission matrix mapped to portals. Owner and admin share the admin portal (owner alone manages plan billing). Instructor maps to the teacher portal. Parent and student get family-facing portals. Superadmin is platform-only. Invites are role-specific emails with an accept link into the right portal.
- Superadmin: tenants, plans, platform users, audit, and broadcasts
- Owner / admin: people, classes, attendance approval, invoices, payments, org settings
- Teacher (instructor): own classes, sessions, and attendance submit
- Parent: linked students, attendance, and issued family invoices
- Student: adult learner timetable, attendance, and own billing views
Technical decisions
We treated tenancy and money as first-class. Prisma owns the schema and migrations. Supabase owns auth, storage, and RLS. App routes enforce role homes and permissions so a parent never hits admin billing APIs.
- Org-scoped data model (organisation_id on classes, sessions, attendance, invoices)
- Permission matrix (can / canAll) for owner, admin, instructor, parent, student, superadmin
- Attendance rate snapshots at submit; GST registration frozen on issue
- Family invoices for guardians; adult learners billed on their own account
- Branch-gated Prisma + Supabase migrations (dev vs prod) on Vercel (syd1)
- Playwright QA coverage for critical centre workflows
What changed
Centres get one operational path from class attendance to issued invoice, with portal boundaries that match how tuition businesses actually staff and bill.
- Attendance events feed draft invoices instead of spreadsheet rebuilds
- Teachers mark; admins approve and issue; parents pay against issued invoices only
- Platform superadmin can manage tenants and plans without entering centre PII tools by default
Stack
Next.js (App Router), TypeScript, Prisma, PostgreSQL on Supabase (Auth, RLS, Storage), Tailwind CSS, Vercel (Sydney), Playwright.
More projects
Explore other work in the portfolio







