Trust guide
How does Raqeem isolate each school’s data?
A clear explanation of institution separation, permissions and the rule against transferring one school’s methods to another.
- Written by
- Raqeem content team
- Product review
- Raqeem product team
Direct answer
Each customer works inside the authorised scope of its institution. One school’s data is not shown to another, and its operating methods, settings or experience are not used to recommend practices to an independent school. Central visibility exists only for a genuinely connected school group and through explicit permissions.
Guide method and boundaries
This guide reflects capabilities reviewed in Raqeem at the stated revision date. It separates available functionality from planned work and does not claim external certification, integration or synchronisation without published evidence.
Isolation starts with the institution boundary
Every operation, record and file should belong to the correct institution, with access limited by the user, role and scope.
Hiding a link in the interface is not enough; access rules must prevent an unauthorised user from reading or changing another institution’s data.
No sharing of school practices
Raqeem does not use a school’s data, internal organisation or operating methods to provide another school with its experience.
There is no comparison between schools or transfer of practices, whether identified, anonymised or aggregated for the purpose of sharing methods.
A school group is a separate administrative case
When one organisation owns several branches, a central user may receive limited visibility when the administrative relationship and permissions are established.
This does not expose branch data to independent institutions or remove each branch’s own scope.
Internal permissions complete the isolation model
After institutions are separated, access inside each one is also controlled: teachers do not need all financial data, parents see only their children and sensitive operations remain restricted.
Permissions should be reviewed when responsibilities change or a user leaves the institution.
Trust questions to ask
- Do access rules prevent cross-institution reading?
- Is every role’s scope defined inside the institution?
- Are school comparisons and practice transfer excluded?
- Is central visibility limited to a genuinely connected group?
- Are permissions reviewed when users change?
Related questions
Does one school benefit from another school’s methods in Raqeem?
No. A school’s methods, settings and experience are not passed to another school and are not used to build cross-institution recommendations.
Can a school group director see its branches?
Yes, only within an established administrative relationship and explicit central permissions, without exposing data to an independent organisation.
Does isolation mean all staff in one school see the same data?
No. Institution separation is combined with internal access control based on role and work scope.
More guides on governance and security
Guides on institutional data isolation, permissions, information protection and timetable conflicts.
Who can do what? Roles, permissions and sensitive actions
Understand role, capability and data scope, then control viewing, creation, editing, deletion, review and approval.
How should a school protect student, family and staff data?
Practical principles for limiting access, isolating institutions, protecting accounts and separating production from testing.
How should a school build a timetable and review conflicts before publishing?
A journey from setup and draft to teacher, class and room conflict checks, then review and publication.