Case Study / 2026
Enterprise Academic Grant, Peer-Review & IPR Governance Platform
Unified research & community service platform spanning 19 modules, 61 relational models, and 138 granular RBAC permissions, replacing fragmented manual grant workflows with audited digital operations.
19
Business Modules
Cross-service grant & IPR domains
61
Database Models
Relational Sequelize/MySQL models
138
RBAC Permissions
Symmetrical UI & API enforcement
E2E + Unit
Verification
Playwright, WIB Audit Log & Bruno
problem
Fragmented Academic Governance
Context
Grant proposals, departmental approvals, external reviewer feedback, progress monitoring, and IPR filings were previously handled across disconnected spreadsheets and static documents, creating version confusion and manual assignment letter bottlenecks.
Constraints
- Enforce strict multi-role boundaries across proposers, department heads, reviewers, and super-admins.
- Preserve auditable WIB timestamps and signature integrity for official PDF exports.
architecture
Symmetric RBAC & Dual-Backend Architecture
interactive diagram
Symmetric RBAC & Dual-Backend Architecture
A React 18 SPA enforces visual guards via <Can> and useRBAC() mapped 1:1 to 138 backend middleware permissions, backed by HTTP-only JWT cookies, CSRF protection, Helmet v8, and a dedicated external research index web crawler.
tradeoffs
Key Trade-offs
Incremental ESM Migration vs Big-Bang Rewrite
Keeping active production traffic on Express v4 CJS while developing a modular TypeScript Express v5 target against the identical MySQL schema avoided downtime across active academic grant cycles.
results
Measured Outcomes
Delivered 19 production modules, canvas-based PDF.js reviewer annotations, automated assignment letter generation, and automated Playwright E2E plus unit test suites verifying audit logging and role boundaries.
Architecture Decisions
ADR 1 / accepted
Enforce 138 Granular Permission Constants Across UI and Middleware
Role-name checks quickly break when institutions introduce hybrid roles (e.g., a lecturer who is also a reviewer and coordinator).
Model authorization around 138 atomic permission keys checked server-side in middleware and mirrored by declarative UI guards.
