How tejas-vetukuri/hrms-4at works
4AT-HRMS is a single-company HR system with a Next.js employee/admin interface and a Django/DRF backend. The principal path is a signed-in user working in an HR screen, through a Next.js API route and proxy, to backend domain handling and a response. The tree shows employee, leave-example, payroll, account and audit modules, alongside frontend attendance, performance and other screens; their backend counterparts are not all present. Edges reflect the sampled proxy behavior and documented stack, not uninspected module internals.
Main entry points: config Django API · proxy.ts Backend proxy · (app) HR screens · core Scope and permissions
Components 18
Next.js interface
- HR screens
frontend/src/app/(app) - Login screen
frontend/src/app/login/page.tsx - Employee routes
frontend/src/app/api/employees - Attendance route
frontend/src/app/api/attendance - ESS profile route
frontend/src/app/api/ess/profile/route.ts - Admin routes
frontend/src/app/api/admin/[...path]/route.ts
Identity and access
- Auth context
frontend/src/lib/auth/auth-context.tsx - Auth routes
frontend/src/app/api/auth - Backend proxy
frontend/src/lib/api/proxy.ts - Accounts and RBAC
backend/accounts
HR domains
- Employee directory
backend/employees - Leave example
backend/example_leave - Payroll
backend/payroll
Django platform
- Scope and permissions
backend/core - Audit records
backend/audit - Django API
backend/config
Other components
- HR user
- Application database
Connections 22
- HR user → Login screen: signs in
- Login screen → Auth routes: submits credentials
- Auth context → Auth routes: requests identity
- HR screens → Employee routes: requests directory
- HR screens → Attendance route: requests attendance
- HR screens → ESS profile route: updates profile
- HR screens → Admin routes: manages HR
- Employee routes → Backend proxy: calls proxy
- Attendance route → Backend proxy: calls proxy
- ESS profile route → Backend proxy: calls proxy
- Admin routes → Backend proxy: dispatches proxy
- Auth routes → Backend proxy: calls proxy
- Backend proxy → Django API: forwards requests
- Django API → Accounts and RBAC: routes identity
- Django API → Employee directory: routes directory
- Django API → Leave example: routes leave
- Django API → Payroll: routes payroll
- Django API → Audit records: routes audit
- Accounts and RBAC → Scope and permissions: uses access rules
- Employee directory → Scope and permissions: uses access rules
- Leave example → Scope and permissions: uses access rules
- Payroll → Scope and permissions: uses access rules