This policy sets out how KarMuqabla works with schools, branches, and campuses — from the first roster import to how student data is handled once a partnership ends.
Overview
A “school partner” is any institution — single campus or multi-branch network — that adopts KarMuqabla for its students through a formal agreement, rather than students registering individually. This includes schools onboarded directly and those migrated from legacy rosters.
Roles & access
| Role | What they can see and do |
|---|---|
| School / branch admin | Oversee all campus users, sections, and activity for their school or branch |
| Teacher | Manage their assigned grades, subjects, and sections; view progress for their own students |
| Parent (school-linked) | View their own children’s activity where a parent account is linked |
| Student | Access content and assessments for their grade and section |
Onboarding & bulk import
Schools onboard through a bulk Excel import process, or migration from a prior system where applicable. The school is responsible for the accuracy of the roster data it submits, including student names, grades, sections, and any guardian contact details provided for parent linking.
Data ownership
Student and staff records provided by a school remain the school’s data. KarMuqabla processes this data solely to operate the platform for that school’s users, under the terms of the partnership agreement, and does not repurpose it for unrelated products or third-party marketing.
Teacher & section management
School admins assign teachers to grades, subjects, and sections. A teacher’s visibility into student progress is scoped to their own assignments — a teacher does not see students outside their assigned sections unless the school admin grants broader access.
Sponsorship & billing
Schools may sponsor access at the branch, campus, or individual student level, depending on the package agreed with KarMuqabla’s CRM team. Billing terms, invoicing schedules, and B2B package details are set out in the school’s individual contract, not in this policy.
Service commitments
- A named onboarding contact during roster setup and initial rollout
- Reasonable uptime for the school-facing dashboard and student app
- Notice ahead of planned maintenance likely to affect classroom use
- A support channel for issues raised by school or branch admins
Offboarding & data deletion
If a school ends its partnership, KarMuqabla will disable access for that school’s accounts and, on request, delete or return the school’s student and staff data within the timeframe set out in the partnership agreement, except where retention is required by law.
Acceptable use for schools
School admins agree to use roster and progress data only for legitimate educational purposes, to keep admin credentials secure, and to promptly report any suspected unauthorized access to student accounts.
School support
For partner schools
Reach your onboarding representative directly, or contact the KarMuqabla school success team through the CRM support channel provided during setup.