Schools running Odoo usually already hold the real data — student records, invoices, attendance lines, exam scores — but have no clean way to expose it to parents. The stock Odoo portal app was designed for sales and invoicing customers, so a parent who logs in sees a generic "My Account" with quotations and orders, not their child's attendance percentage or latest report card. Front-office staff end up fielding the same calls every week ("what's the fee balance?", "did my son attend Tuesday?", "when is the exam?"), and there is no self-service surface that ties a res.partner to the specific student records that partner is allowed to see. That gap — data exists, safe access does not — is exactly where Odoo native runs out of road.

The Parent & Student Portal is a productized module ECOSIRE builds on top of base, mail, website, portal and account. We model a student profile (extending or linking res.partner) plus a parent–child relationship so a single parent login resolves to one or several children and switches context between them without re-authenticating. On top of that sit portal-facing QWeb pages for attendance (a @api.depends computed percentage with threshold-based absence alerts fired via automated actions), fee statements that read straight from account.move / account.move.line with a pay-now flow through your configured Odoo payment provider, exam results with report-card and transcript PDFs rendered as QWeb reports, timetable and academic-calendar views, homework/assignment listing with attachment upload, an announcements/circulars feed with per-recipient read receipts, and a teacher–parent messaging thread built on the mail.thread backbone so every conversation is logged against the student and searchable from the back office.

The security model is the load-bearing part, and it is where a typical off-the-shelf apps.odoo.com module tends to be thin. Access is enforced with ir.model.access.csv for base CRUD plus ir.rule record rules that scope every portal read to student_id.parent_ids = user.partner_id (and the student's own records for a student login), so no parent can ever URL-guess their way into another family's fees or grades. Controllers extend Odoo's /my portal routes with the same domain filters, and the whole thing ships as a proper module with a versioned __manifest__.py. It runs on Odoo Community or Enterprise; Enterprise-only surfaces (such as advanced studio-built views or specific accounting localizations) are handled only when your edition supports them, and we tell you up front which capabilities depend on which edition. We support Odoo 17.0, 18.0 and 19.0, and the same portal data is reachable over the XML-RPC / JSON-RPC API if you later want a native mobile app to consume it.

Because this is build-to-order, nothing is a shrink-wrapped download. After a short scoping call we confirm which capabilities you need, map them to your existing student/attendance/exam models, then build, test on a staging copy of your database, and hand over installable source, documentation and training. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); multi-company or multi-branch school groups, deeper localization of report cards and fee documents, SMS/WhatsApp alert integrations, and migrating large volumes of historical student and result data increase the quoted scope. You get a fixed quote after the scoping call — never a surprise on delivery.