University ERP / Student Management System
A role-based ERP serving admissions, academics, and finance for a university e-portal.
4
distinct roles with isolated permissions
8+
modules: admissions to reporting
100%
registration flow behind validation + reCAPTCHA
Tech Stack
The Challenge
Al-Kawthar University needed to move manual admission and onboarding workflows into a single e-portal. Administrators, faculty, students, and staff each needed a different view of the same data — with no way to leak records across roles. Registration was the highest-traffic surface and the most abuse-prone, so forms needed airtight validation and bot protection without hurting conversion.
Approach
- 1
Modelled RBAC around a permission matrix agreed with each department before writing any UI, so frontend routes, API middleware, and database queries all checked the same capability names.
- 2
Rebuilt the registration and onboarding forms as responsive, accessible flows: field-level validation, password strength rules, and server-side re-verification of every client check.
- 3
Added reCAPTCHA to the public entry points and rate-limited sensitive endpoints to blunt bot registrations.
- 4
Shipped frontend accessibility and UX improvements (keyboard navigation, clear error messaging, mobile layouts) to reduce support tickets from applicants.
Technical Highlights
One permission vocabulary
Roles, capabilities, and resource scopes were defined once and shared between the Next.js frontend and Express API, eliminating the classic drift where a UI hides a button the server still allows.
Onboarding as a state machine
Student onboarding (form → verification → document review → enrollment) was implemented as explicit states, making half-finished applications recoverable and auditable.
Reporting without duplication
Attendance, examination, and fee reports read from shared PostgreSQL views instead of module-specific copies, so numbers reconciled across departments by construction.
What I Learned
Institutional software lives or dies on the permission model — getting it right early prevented months of patching later.
Public-facing forms are security surfaces; client validation is UX, server validation is truth.