Problem
Many Laravel systems that support multiple stakeholder types struggle with guard ambiguity, cross-guard permission mistakes, inconsistent dashboard routing, session conflicts, and environment-specific deployment issues.
← Back to Projects
Laravel Project
Laravel Stakeholder RBAC Infrastructure
A reusable Laravel 11 infrastructure artefact for multi-stakeholder systems, demonstrating multi-guard authentication, stakeholder-aware RBAC, deterministic dashboard routing, Redis-backed session/cache/queue separation, and Docker Compose-based deployment.
Solution
I developed a reusable Laravel 11 infrastructure artefact inspired by the multi-stakeholder authentication and RBAC challenges encountered in the NKA Student Portal project. Unlike NKA, which is a domain-specific student administration system, this artefact isolates the reusable infrastructure layer for deterministic multi-guard authentication, Spatie role-based permissions, stakeholder-aware dashboard routing, single active authentication context handling, Redis-backed state separation, and Docker Compose-based reproducibility.
Technologies Used
Engineering Highlights
- Reusable Laravel 11 infrastructure artefact archived as a professional and academic reference project
- Multi-guard authentication architecture for stakeholder-specific access boundaries
- Spatie Laravel Permission integration with guard-aware role and permission handling
- Deterministic guard resolution to reduce cross-guard authentication ambiguity
- Stakeholder-aware dashboard routing based on authenticated guard and role context
- Guard-aware email verification flow across web, student, and employer authentication contexts
- Single active authentication context handling to reduce session confusion across stakeholder areas
- Redis used as a centralised state layer for sessions, cache, and queues using separated logical databases
- Docker Compose environment with Laravel, Nginx, MariaDB, Redis, Node/Vite, and phpMyAdmin
- Documentation-first engineering approach with architecture notes, supplementary evidence, ADRs, and runtime verification material
- Verified across Linux Docker Engine and Windows Docker Desktop environments
What I Learned
- Strengthened understanding of reusable infrastructure design beyond a single application domain
- Improved multi-guard authentication design using explicit guard boundaries and deterministic routing
- Practised RBAC correctness by preventing cross-guard role and permission assignment issues
- Learned how ideas from the NKA Student Portal could be separated into a reusable Laravel infrastructure artefact
- Designed Redis-backed session, cache, and queue separation for predictable containerised runtime behaviour
- Improved Docker Compose discipline for reproducible Laravel development environments
- Practised documentation-driven engineering by preparing architecture notes, runtime evidence, and research artefact material
- Learned how to package software infrastructure as a reusable academic and professional reference artefact