School Management

What it does

School Management turns Odoo into a school back office. You set up the academic frame once, which is the academic year and its terms, the grade levels, the classes and sections, and the subjects. After that the daily work has a home: admit students and record their guardians, assign a class teacher and allocate subjects to teachers, build the weekly timetable, take attendance, enter examination marks, and issue fee statements.

Around that core sit the registers a school actually keeps: transport routes and student subscriptions, hostel buildings, rooms and bed allocations, and a library catalogue with issues and returns. Student ID cards, academic report cards and fee statements print as PDFs.

Fee tracking is deliberately operational. Statements record the amounts you enter by hand and show what is outstanding. No journal entries, taxes or reconciliation are created, and the description says so plainly rather than implying an accounting integration that is not there.

The part that is easy to get wrong in a school system is who can see what, so that is where the work went. There are two roles, Teacher or Faculty and Administrator. A teacher reaches a class either by being its class teacher or by holding a subject allocation in it, and classes outside that are not visible at all rather than merely read only. Fee statements and student medical notes are administrator only. All of this is enforced by record rules and access rights, which means it holds over the API and not just in the interface.

The second thing is historical records that stay true. A fee statement, a report card and a library loan each capture the student's class at the moment they are issued, and do not follow a later change. Promoting a student to the next class therefore leaves last term's documents exactly as they were, still reachable by the teacher who recorded them. A transport subscription captures its monthly fare the same way, so a later price change does not rewrite historical subscriptions.

Lifecycle locks work the same way. Submitting an attendance register locks its lines, and completing an exam locks its marks; reopening either is an administrator action. Those locks live in the model's write method rather than in the view, so hiding a button is not what is holding them.

The module depends only on base and web. There is no accounting dependency and no Enterprise requirement, so it installs on Community and Enterprise alike. It ships with 178 automated tests, including access-control, write-guard and historical-data suites, and demo data that puts two classes under two different teachers so the access boundary can be seen working rather than taken on trust.

Who it's for

Schools, colleges and training institutes that already run Odoo, or want to, and need student administration in the same database as the rest of the business. It suits an administrator who wants teachers to have real, scoped access to their own classes without being able to reach another teacher's students, results or the fee ledger.

It is not a parent or student portal, and it is not an accounting product. If you need families to log in and pay online, this is the record-keeping layer underneath that, not the thing itself.