Branch isolation
Branch context is resolved before permission checks and cross-branch access returns a 404.
Security
Student records and school payments need stronger boundaries than ordinary SaaS data.
Schools handle children, guardians, staff, finances, and learning records. Jibar builds branch-safe access, audit history, and verified payments into the first foundation.
Team permissions
Roles are scoped to branches so a bursar, registrar, teacher, or support agent only sees the right school data.
Payment verification
Paynow callbacks and return-page polling converge on an idempotent payment completion path.
Account safety
Verified email, password reset, password confirmation, and two-factor-ready admin roles stay in the auth flow.
Audit history
Sensitive changes such as network creation, branch updates, payment starts, and role changes are recorded.
Student data care
The platform treats student records, guardian contacts, billing history, and learning access as sensitive school data.
CSRF protected app routes
Paynow callback exceptions only
Audit logs on sensitive changes