Jova School
A school platform serving many schools from one codebase: each school gets its own web address, is set up automatically when it registers, and keeps its data separate from the others.
- Type
- Internal and SaaS
- Stack
- Laravel
- Role
- Backend developer.
The problem
One deployment had to serve several schools, each with academics, attendance, finance, staffing, extracurricular records and admissions, and no school could see another school's data.
What I decided
- Kept one shared schema with a school identifier on every tenant table, enforced in the query layer with Eloquent global scopes, instead of a database per school.
- Provisioned a new school in a single transaction: the school record, five role types, the full module and action authorization matrix, a master account and the default payment groups.
- Enforced access by module and action (view, add, edit, delete) resolved from the route name, with a separate authorization matrix for every school.
Where it landed
The platform covers the full school cycle in one codebase: admissions, academic planning, attendance, grades and report cards, tuition with instalments, staffing and payroll, and extracurricular reports. The subscription layer, with plans, coupons and billing, sits in a separate superadmin panel.
All projectsNext project: Jova Resto
Client systems stay private: no source code, internal URLs or production screenshots appear here. Every figure comes from the repositories or a read-only count on the production database.