How the modules connect
Most "why can't I do this?" questions are a dependency that has not been set up yet. This is the order things have to exist in.
Set up the organisation first
Company details → Business units → Roles and permissions
These three underpin everything else. A department, business unit or role has to exist before you can assign someone to it.
People
Add an employee — assigns a role, a business unit and a salary template. Creating the employee record is what makes them visible to every other module.
Attendance feeds payroll
Punch in and out, leave, work from home and regularization settle the period. Payroll reads that settled attendance, so corrections belong before the pay run, not after.
Payroll
Components and templates → Salary details → Payslip templates → Run payroll
The readiness check enforces this chain. It fails when a salary structure, a payslip template or an employee's salary data is missing. The run produces payslips, the bank salary file, PF ECR and Form 138 preparation.
Hiring
Create a job → candidates → offer → onboarding. The outcome of hiring is a person who becomes an employee in People.
Projects
Add a client → Create a project → Client staffing → Timesheets → billing and analytics.
The client must exist before the project. This is the single most common blocker in Projects.
Learning
Create a course → enrol → quiz or certification → the result shows on the employee profile.
Helpdesk and operations
Support tickets, operations tickets, assets and documents.
The dependencies worth remembering
| You want to | It first requires |
|---|---|
| Create a project | The client to exist |
| Run payroll | Salary template → employee salary details → payslip template |
| Generate a payslip | A finalized pay run |
| Assign someone to a business unit | The business unit to exist |
| Staff a project | The project to exist |
Related: Terminology · Glossary