Tenant isolation
School data is designed around tenant-scoped access. Staff should only see the students, classes, and families that belong to their own school.
Security approach
Student data deserves quiet, strict, boring security.
Min Dugsi is intended for Quran schools handling sensitive student and family information. That means security should be built into the product shape, not added later as decoration.
Role-based access
Teachers, school admins, parents, students, and platform operators should each have narrow permissions and clear boundaries.
Sensitive-data discipline
Student, family, and contact information must be treated as protected data with least-privilege access, auditability, and careful retention.
Controlled onboarding
New schools should enter through a verified onboarding flow, not immediate unrestricted self-provisioning.
Security rules for the platform skeleton
- Protect all tenant data behind restrictive row-level access rules.
- Keep audit logs for sensitive admin and student-data changes.
- Minimize public attack surface and avoid unnecessary anonymous endpoints.
- Prefer link-based secure onboarding and recovery over weak code-based flows.
- Review data retention, export, deletion, and operator access as explicit policies.