Security is part of the SHULE EXTRA design.
School systems contain sensitive operational, academic and financial information. SHULE EXTRA is designed around tenant isolation, authorization and auditable workflows.
Tenant Isolation
Each school operates within its own tenant workspace. Access to tenant-scoped records should validate the active school before data is returned or modified.
Role-Based Access
Users receive access according to school membership, roles, direct permissions and authorized scope.
- School users only receive authorized functions.
- Sensitive actions use separate permissions.
- Parent access is limited to linked children.
- Financial corrections use controlled workflows.
Authentication & Passwords
Passwords should be handled using secure password hashing provided by the authentication framework. Production deployments should use HTTPS and secure session controls.
Financial Integrity
Posted financial history should not be silently rewritten. Reversals, adjustments and approvals maintain a clearer audit history for sensitive transactions.
Examination Integrity
Examination status, marks changes, approvals and result publication should follow authorized workflows and maintain appropriate history.
Provider Credentials
Production credentials for services such as messaging, payments, email or other integrations should be stored outside source code using secure environment configuration.
Reporting Security Concerns
If you believe you have identified a security issue, do not publish sensitive data or attempt to access information that is not yours. Contact WORNTECH SOLUTIONS through the official Contact page.