FlowHCM
An original FlowHCM-like HRMS being built for a client to manage organisation structure, employees, documents, accounts and permission-controlled operations in one product.
Engineering decisions behind FlowHCM.
Interfaces, application logic and production experience move together—not as isolated layers.
What I worked on.
I am building the frontend and backend as a local client project using Next.js, React and TypeScript with a Laravel REST API. The current implementation covers authentication and access management, organisation setup, branches, departments, designations, employee records, employee documents, employee accounts and role assignment. Attendance, leave and payroll are intentionally shown as future modules, not finished features.
The project is an active local build for a client. Core account, access, organisation and employee-management work is implemented; there is currently no public deployment or GitHub repository, and the remaining HR modules are still in development.
What the project includes.
- Authenticated dashboard and protected application navigation
- Organisation setup with branch, department and designation management
- Employee CRUD, profile details and document workflows
- Document view, upload, update, verification and download permissions
- Employee account creation, activation, role assignment and password reset
- Role and permission system covering dashboard, organisation, employees, reports, users and settings
- Attendance navigation and permission groundwork
- Clearly marked future tabs for attendance summaries, leave and payroll
How the work was approached.
- 01
Kept the product original and requirement-led instead of copying a proprietary HRMS interface or codebase.
- 02
Separated organisation structure, employee records, documents and accounts into clear modules so permissions can be applied at the correct level.
- 03
Used Laravel Sanctum and granular Spatie permissions to support authenticated, role-aware workflows across the application.
- 04
Left attendance, leave and payroll visibly marked as pending so the portfolio does not present planned work as complete.
Technology used on this project.
The stack below reflects the tools and platform involved in my contribution—not a generic list of everything I know.
Next.js
React
TypeScript
Laravel REST API
PostgreSQL
AWS S3 / compatible storage
Docker