| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Discuss (mail) • Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 4692 |
| Technical Name |
schoolos_compliance |
| License | OPL-1 |
| Website | https://bbtech.ae/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Discuss (mail) • Employees (hr) |
| Community Apps Dependencies | Show |
| Lines of code | 4692 |
| Technical Name |
schoolos_compliance |
| License | OPL-1 |
| Website | https://bbtech.ae/ |
This is a dependent SchoolOS application. It runs on top of the main SchoolOS app (the unified data model, roles and portals). Get the complete SchoolOS bundle - every module, every portal, every report - in a single license.
|
SchoolOS - Compliance
Data-protection toolkit for Odoo 19 - DSARs | Consent Register | Retention Policies | Breach Log | GDPR / PDPL-style record-keeping
SchoolOS Compliance is a data-protection and privacy record-keeping toolkit for Odoo 19. Log and track Data Subject Access Requests (access, rectification, erasure, portability and objection) with computed statutory due dates and an overdue flag; maintain a consent register for photo / media, data-processing, marketing, trip, medical and third-party-sharing consents and withdrawals; catalog retention policies per data category; and keep a breach / incident log with severity, containment and authority-reporting status - all on the same student, parent and staff records as the rest of SchoolOS. It is a record-keeping aid, not legal advice, and never deletes data on your behalf.
Who is this for?
- Data Protection Officers and compliance leads
- School administrators handling DSARs
- Registrars maintaining consent records
- Schools and school groups under GDPR / PDPL-style regimes
- Leadership tracking breach incidents and reporting
- Odoo consultants and developers extending the suite
Key Benefits
DSAR Lifecycle & Deadlines
Track every Data Subject Access Request from receipt to fulfilment, with a computed statutory due date and an automatic overdue flag.
Consent Register
A single register of granted and withdrawn consents per subject and type, with a one-click withdrawal that stamps the date.
Retention Policy Catalog
Document how long each data category is kept and what should happen afterwards - a catalog that never deletes data itself.
Breach Incident Log
Record incidents with severity, affected counts, containment notes and whether they were reported to the supervisory authority.
Feature Highlights
DSAR Requests
Log access, rectification, erasure, portability and objection requests against a student, parent or staff subject.
Computed Due Dates
A configurable response window (default 30 days) computes the due date and raises an overdue flag automatically.
Request Workflow
New → In Progress → Awaiting Subject → Fulfilled / Rejected, with status-bar buttons and chatter tracking.
Consent Types
Photo / media, data processing, marketing, trips, medical and third-party sharing - captured per subject.
One-Click Withdrawal
Withdraw a consent in one click; the system stamps the withdrawal date and flips the granted flag.
Retention Catalog
Per-category retention months and intended action (anonymize / delete / review) - documentation only, never destructive.
Breach Severity
Low / medium / high / critical severity with affected-subject counts and an open / contained / closed workflow.
Authority Reporting
Flag whether a breach was reported to the supervisory authority and on what date.
Multi-School Scoping
Every record is company / school scoped via record rules, so each school sees only its own compliance data.
Auto Sequences
DSARs and breaches get clean DSAR/ and BREACH/ reference numbers automatically on creation.
End-to-End Workflow
1 | Log a DSAR against the data subject; the due date and overdue flag compute automatically |
2 | Work the request through its states, then fulfil or reject with resolution notes |
3 | Maintain the consent register, withdrawing consents in one click when subjects ask |
4 | Catalog retention policies per data category and log a review when each period elapses |
5 | Record any breach incident, contain it, and track authority reporting through to closure |
Role-Based Experience
Compliance Officer
Manages DSARs, the consent register, retention policies and the breach log day to day.
Principal
Reads compliance records for oversight without editing them.
Super Admin
Has read visibility across all compliance models for governance.
Data Protection Officer
Uses the toolkit as the central record of DSARs, consents, retention and breaches.
Reports & Dashboards
- DSAR list with overdue highlighting, filters and group-bys
- Consent register grouped by type, source and subject
- Retention policy catalog by intended action
- Breach log by severity and status
- Authority-reporting view for breach incidents
- Chatter audit trail on every record
- XLSX exports across every compliance list view
Integrates with SchoolOS
This application is part of the SchoolOS suite and requires the main SchoolOS application (the unified data model, roles and portals). SchoolOS - Compliance plugs into the same student / staff / academic records and the Student / Teacher / Parent / Manager portals, so every action updates one source of truth and role-based access is enforced consistently. Get the complete suite here:
Technical Quality
- Role-based and record-rule access control
- Multi-school and multi-curriculum ready
- Portal-ready (Student, Teacher, Parent, Manager)
- Dashboard-ready with KPI tiles
- Report-ready (PDF + XLSX)
- Clean, extendable Odoo 19 architecture
- Runs on Odoo Community and Enterprise
- Deploy on Odoo.sh or on-premises
Customisation, Implementation & Mobile Apps
Customisation & Implementation: Binary Bridge Technology Services provides full customisation, configuration, data migration, training and on-the-ground implementation for SchoolOS. To scope your rollout, contact us at odoo@bbtech.ae or WhatsApp +971 56 128 6321.
Native iOS & Android mobile apps for all SchoolOS portals are available as a separate add-on (not included in the suite license). See the main SchoolOS listing for mobile-app pricing and options.
Built for GCC & international schools
SchoolOS is a unified school-management platform for the Gulf and international K-12 market - multi-curriculum (CBSE | IB | British | American | MOE | Cambridge), multi-school and multi-currency, with Arabic / RTL interfaces and an optional Hijri calendar. It runs entirely on Odoo 19 Community or Enterprise, on Odoo.sh or on-premises, with full Odoo accounting built in. Built and tested for GCC schools - and fully usable by any school worldwide.
Why SchoolOS vs the alternatives
How an integrated, GCC-ready Odoo suite compares with a generic SIS or a stack of spreadsheets and point tools.
| Capability | SchoolOS | Generic SIS | Spreadsheets / point tools |
|---|---|---|---|
| Single unified student / staff record across every module | ✓ | - | - |
| Multi-school & multi-company scoping with record rules | ✓ | partial | - |
| Role-based Student / Parent / Teacher / Admin portals | ✓ | partial | - |
| Fees & accounting that post to Odoo | ✓ | - | - |
| Arabic / RTL interface + Hijri calendar option | ✓ | - | - |
| Runs on Odoo 19 Community & Enterprise | ✓ | partial | n/a |
| Multi-curriculum (CBSE / IB / British / American / MOE) | ✓ | partial | - |
| One vendor, one stack, audited ISO processes | ✓ | - | - |
Frequently asked questions
About Binary Bridge
Binary Bridge Technology Services is an Odoo implementation and product partner based in the United Arab Emirates. We have delivered solutions across 36+ industries, implemented for 256+ clients, and bring 10+ years of Odoo ERP implementation and development experience. Every engagement follows audited quality and data-security processes.
Ready to bring your school online?
Talk to Binary Bridge for implementation, customisation and on-the-ground rollout support - or get the Complete SchoolOS Bundle now.
Screenshots
This app is sold only as part of the complete SchoolOS bundle
Every SchoolOS module is built on the shared SchoolOS core and works together as one system - installed on its own, a single app has limited use. To get the full, integrated value, purchase the complete SchoolOS suite (one unified licence, USD 12,500) rather than this module alone.
Get the Complete SchoolOS Suite →Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module