Security and data protection

Who can see what, and why

A school hands over its students' names, its parents' phone numbers and its own bank position. These are the controls that decide who inside your school can reach each of those.

Role templates and permission levels

  • Four permission levels with reusable role templates rather than per-user guesswork
  • Each report can be granted to a role separately
  • A teacher starts on an academic preset that excludes fee collections, payroll and other employees' HR data
  • Seeing every employee's attendance requires an explicit high-risk HR permission

Scope, not just permissions

  • Access is bound to campus, class and section, so a permission only applies where the user is assigned
  • Selecting a campus constrains every dependent filter beneath it
  • Teachers see only their assigned registers
  • Filters on reports follow the same scope rules

Identity and accounts

  • Guardian account creation checks linked family and student details instead of blindly creating another login
  • Student accounts are permanently limited to their own record
  • Teacher logins are created with the teacher record so identities are never left unlinked
  • An administrator password reset revokes all existing sessions for that user

Audit and protected actions

  • Fee adjustments, waivers and fine changes remain auditable
  • Salary payment is protected to one per employee per month, and the expense is generated automatically to prevent duplicates
  • Closing a payroll month can only be reversed with a recorded reason
  • Published exam results lock marks until they are explicitly unpublished
  • Imported marks are written only after human review, with an audit event
  • Legacy import rollback is blocked once later payments or allocations depend on the data

A disabled feature is removed from navigation, APIs and settings rather than hidden on screen. Turning a module off actually takes it away.

What boards ask

On SQL Server behind a VPS. The platform is multi-campus and SaaS-controlled, so your school's records sit under your own subscription and scope rules.

Yes, at any time while your subscription is active. Students, fees and results all export, and those files stay yours if you stop using SchoolPortal.

Support access exists so we can help when something breaks. TODO Zaid: state your actual policy here, including whether support access is logged and whether it needs the school to approve it. Vague answers on this question lose deals.

TODO Zaid: put your real backup schedule and retention period here, and say where backups are stored. This is the single most common security question from a school board.

Employee records carry a leaving date and status, and a student or staff account can be reset or revoked from Users and Roles. Sessions end when the account is reset.

A parent sees their own children only: profile, vouchers and payment history, monthly attendance, published results and homework. Nothing about the school's administration, other families or staff. Multi-child access is an option a school switches on, and it is limited to that family.

Send us your school's security questions

If your board has a checklist, send it over and we will answer it line by line.