A branded website portal that gives parents and students one secure login for attendance, fees, exam results, timetables and teacher messaging. ECOSIRE builds, installs and supports it on your Odoo — made to your school's records and workflow, not a generic download. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $349.00 USD; request a quote for a scoped proposal.

A branded website portal that gives parents and students one secure login for attendance, fees, exam results, timetables and teacher messaging. ECOSIRE builds, installs and supports it on your Odoo — made to your school's records and workflow, not a generic download.
لا حاجة للدفع الآن. يؤدي هذا إلى إرسال طلب عرض سعر إلى فريقنا — وسنتواصل معك عبر البريد الإلكتروني بالأسعار والخطوات التالية.
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.
Student profile model extending/linking `res.partner`, with parent–child relations resolving one login to multiple children and a context switcher
Portal user provisioning that maps a `res.users` portal account to its allowed student records via `ir.rule` record rules (`student_id.parent_ids = user.partner_id`)
Attendance page with a `@api.depends` computed presence percentage per term/subject and threshold-based absence alerts via automated actions (ir.cron / base.automation)
Fee statement, aged balance and invoice list read directly from `account.move` / `account.move.line`, filtered per student
Pay-now flow wired to your configured Odoo `payment.provider`, reconciling back to the correct `account.move`
Exam results, report cards and transcripts rendered as QWeb PDF reports with your school's letterhead and grading scheme
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 2–4 weeks from confirmed scope. Pricing starts from $349 (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.
Wants to raise parent engagement and cut repetitive front-office calls by giving families a single self-service window into attendance, fees and results — without exposing one family's data to another.
Needs parents to see their own fee statements and pay online so cash reconciliation flows back into `account.move` automatically, instead of re-sending balances by phone and email.
Wants one login that covers all their children, showing attendance, upcoming exams, results, homework and a direct message thread to teachers — on their phone.
Self-serves timetable, assignments with upload, results and transcripts through their own scoped portal login, seeing only their own records.
قم بشراء الترخيص من موقع ecosire.com وقم بتنزيل وحدة Parent & Student Portal ZIP من لوحة تحكم حسابك.
قم باستخراج ملف ZIP إلى مجلد إضافات Odoo المخصصة على الخادم (أو تحميله عبر التطبيقات > التثبيت من ملف على Odoo.sh / runbot).
قم بتنشيط وضع المطور، وافتح التطبيقات، وانقر فوق تحديث قائمة التطبيقات، وابحث عن Parent & Student Portal، ثم اضغط على تثبيت.
افتح القائمة الجديدة، والصق مفتاح ترخيص ECOSIRE الخاص بك، وقم بتوصيل أي بيانات اعتماد خارجية (Shopify، وAmazon، وStripe، وما إلى ذلك)، ثم احفظها.
قم بتشغيل اختبار الاتصال المدمج، وقم بمزامنة أول 10 سجلات لديك، وقم بجدولة عملية cron المتكررة. اتصل بالدعم إذا فشل أي شيء.
| المعيار | ECOSIRE | بناء مخصص | منافس | أودو الأصلي |
|---|---|---|---|---|
| Parent–child linking (one login, multiple children) | Built as a first-class relation with a context switcher | Possible, but you design and test the data model yourself | Often single-student focused; multi-child support varies | |
| Data access security | `ir.rule` record rules + scoped `/my` controllers, reviewed | Only as strong as your team's rule-writing and testing | Present but generic; edge cases depend on the vendor | |
| Attendance, results, fees in one place | Unified portal pages tied to your existing Odoo records | Achievable but every page is bespoke build effort | Covers common cases; may not match your exact models | |
| Fit to your school's models & documents | Mapped to your students, grading scheme and letterhead | Fully yours to define, at full build cost | Fits the vendor's assumptions, not necessarily yours | |
| Online fee payment | Pay-now via your `payment.provider`, reconciled to `account.move` | You wire and test the provider integration yourself | Sometimes included; reconciliation depth varies | |
| Teacher–parent messaging | `mail.thread` threads logged against the student | Build on `mail.thread` yourself or bolt on external chat | May use its own messaging store, harder to audit | |
| Delivery & ownership | Built, tested on staging, source + git handover, support window | In-house time and maintenance burden on your team | Download + your own install; support per vendor policy | |
| Ongoing changes & upgrades | Quoted scope; you hold the repo and can extend it | Your developers own all future work | Depends on vendor roadmap and version support |
No. It is build-to-order. ECOSIRE builds the module against your school's existing Odoo records (students, attendance, exams, invoices), tests it on a staging copy of your database, then installs and hands over the source. There is no instant download.
Typically 2–4 weeks from confirmed scope. After the scoping call we agree exactly which capabilities are in your version; the timeline depends on how many of the twelve capability areas you need and how much of your existing data has to be mapped and migrated.
Pricing starts from $349 as an indicative single-company base scope. Drivers like multi-company/multi-branch school groups, deep localization of report cards and fee documents, SMS/WhatsApp alert integrations, or large historical-data migration increase the quote. You get a fixed quote after a short scoping call — never a surprise on delivery.
Access is enforced server-side with `ir.model.access.csv` plus `ir.rule` record rules that scope every portal read to the logged-in partner's own children (`student_id.parent_ids = user.partner_id`). The extended `/my` controllers re-apply the same domain, so a parent cannot URL-guess into another student's fees, results or documents.
Yes — it runs on Odoo Community or Enterprise, on versions 17.0, 18.0 and 19.0. Some surfaces depend on your edition or installed localization (for example specific accounting localizations); we confirm during scoping which capabilities your edition supports and build only those, telling you up front.
Every build includes a post-go-live support window for defect fixes and configuration questions, and you receive the full git repository so your team can extend it. Version upgrades (e.g. 18.0 → 19.0) or new capabilities are quoted as additional scope.
Yes. The pay-now flow is wired to your configured Odoo `payment.provider` and reconciles back to the correct `account.move`, so payments land against the right student invoice and appear in your accounting without manual matching.
A branded website portal that gives parents and students one secure login for attendance, fees, exam results, timetables and teacher messaging. ECOSIRE builds, installs and supports it on your Odoo — made to your school's records and workflow, not a generic download.