A learning management system for multi-campus colleges and group operators

OpenEduCat enforces campus segregation through Odoo-style record rules (row-level security) tied to campus security groups. Every model with multi-campus relevance — students, enrollments, gradebooks, attendance — carries a campus_id field, and access rules filter reads/writes by the user's campus membership. The rules apply uniformly across ORM, JSON-RPC, and reporting layers, so a Campus B registrar API call cannot exfiltrate Campus A data even with valid credentials. For groups with regulatory isolation requirements (FERPA cohort separation, GDPR data residency per state), we also support separate-database-per-campus topology with a shared identity layer.

Share by default, clone by exception. Sharing means each campus links to a single canonical course record from the group library, so a syllabus or rubric update at the center propagates instantly to all linked sections. Clone when a campus needs to diverge permanently — for example, a regional accreditation body mandates different learning outcomes, or a campus runs a hybrid version of an otherwise residential course. The platform tracks clone lineage so you can later diff and reconverge if the divergence is resolved. Most groups end up with 70-85% shared and 15-30% cloned content.

For most 3-15 campus groups, a single multi-tenant deployment is the right architecture: lower TCO, real-time consolidated reporting, easier identity federation, and a single upgrade path. Separate instances per campus make sense only when (a) campuses span jurisdictions with conflicting data-residency law, (b) one campus runs a fundamentally different academic calendar or grading scale that materially complicates the shared schema, or (c) M&A integration is mid-flight and you need a clean cutover window. In separate-instance topology, OpenEduCat supports a federated reporting layer via the API so the group office still gets consolidated dashboards without a shared transactional DB.

Yes. Academic structure — terms, sessions, grade scales, credit systems, transcript formats — is configurable per campus. A US campus on a semester GPA system and an Indian campus on a CGPA + percentage system coexist on the same instance with no field-level conflicts. Curriculum maps, prerequisite trees, and degree-audit rules are also campus-scoped. Where the group office wants standardization (for example, a uniform learning-outcomes taxonomy across all campuses for accreditation reporting), it can be enforced at the parent catalog layer while leaving delivery-level decisions to each campus.

Yes. The OpenEduCat mobile app (iOS, Android) and parent portal resolve the user's institution from their identity, so a parent with children at two campuses in the same group sees both children in one session, with grades, attendance, fees, and announcements pulled from the correct campus context. Push notifications are routed per campus so a Campus 1 closure alert doesn't ping Campus 2 families. Branding can be group-wide (unified marque), per-campus (each campus's own logo and palette in the app), or a hybrid using white-label theming.

OpenEduCat uses a per-active-learner model with group-tier discounts that kick in at consolidated enrollment thresholds (typically 5k, 15k, and 50k learners). Group CIOs see a single contract and a single invoice rather than per-campus procurement. The EDUCAUSE 2024 Enterprise IT Survey reports that consolidating learning platforms across a multi-campus system typically yields 18-30% TCO reduction versus running per-campus LMS contracts, mostly from eliminated duplicate licensing, integration, and L1 support staffing. We can model a specific group TCO during scoping using your current per-campus contracts as the baseline.