HR: People, attendance and leave on the same steel as operations.
Employee records, attendance capture, leave requests and approvals, and payroll-ready exports.
Employees, contracts, attendance, leave balances and disciplinary notes, each permissioned.
Role-scoped visibility, approval chains for leave and overtime, and change history.
Standalone. HR records are not payroll compliance; exports feed your payroll provider.
Employee master imported first; attendance rules configured; first month run in parallel.
Role and approval models from HR power the permission checks every other module enforces.
Your records stay exportable in open formats before and after cancellation. Offboarding follows a documented export and deletion path.
Yes. Masters first, open transactions second, using sample templates from your Blueprint's data-readiness block.
Role-based permissions with approval thresholds; every sensitive action lands on the audit trail.
The Blueprint states scope, dependencies and exclusions explicitly before you activate anything.