Security
Student data handled with care
Schools trust SIMS with records about children. These are the safeguards built into the application.
Role-based access
Every screen and action requires a specific permission. Roles are built from those permissions and edited from a screen.
Checked on the server
Permissions are checked on the server for every page and every action. Hiding a menu item is a convenience, not the security.
Changes apply immediately
Permissions are re-read on every request, so removing someone's access takes effect on their next click.
Private file storage
Documents and images are stored in a private Amazon S3 bucket. Uploads and downloads use signed links that expire in minutes.
Audit trail
Every admissions transition, comment and attachment is recorded with who did it and when.
Encrypted email credentials
Your school's SMTP password is encrypted before it is stored.
Validated data
All input is validated on the server against the same rules as the form. Grade levels, sections and courses are real linked records.
Dedicated database
SIMS runs as its own application with its own PostgreSQL database. It isn't a shared, generic platform.
Least privilege
Everyone sees only what they need
Each role is limited to its own work, and the server enforces those limits.
- Teachers only see, take attendance for and grade their own classes.
- Students only see their own schedule, coursework, grades and attendance.
- Applicants only see their own application.
- Report cards and the school-wide reports are for administrators.
- Super admins manage the school but can't act as a student or applicant.
Built with
A modern, widely used stack
Questions about data protection?
We're happy to walk your IT team through how SIMS handles access, files and records.