HRMS · People

One record,
read by everything.

The employee master is not just an HR list — it is what the CRM assigns leads against, what Projects staffs a team from, and what payroll pays. Getting it right once is what stops four systems disagreeing about who works here.

The list that drifts. A separate directory per app is one that is wrong within a quarter, and the leavers are what nobody removes.

Structure

Departments, designations, offices.

Hierarchical departmentsA structure that matches the company rather than a flat list, and one the whole platform reads.
DesignationsHeld as records so a title change is an event rather than a typed string that varies by who typed it.
Offices with geofencesThe same office record that attendance validates a punch against and that payroll takes its structure from.
Managers from reporting linesHaving direct reports is what makes someone a manager, rather than a separate flag somebody forgets to set.
When people move

Transfers, with the history kept.

Transfer as a recordBetween offices, departments or managers — recorded as an event with a date, not an overwrite.
History survivesWhich matters when an old payslip has to be explained against the office and structure that applied at the time.
Bulk manager changesReorganisations happen to many people at once, and doing them one at a time is how records get missed.
The details payroll needs

IDs and banking.

Statutory registration IDsPF, ESI, UAN and the rest held against the employee, because the payroll run and the filing both need them.
Banking detailsWhat the bank file is built from, kept on the employee rather than in a parallel sheet.
Nearby

Related capabilities.

Payroll · Recruitment · Employee self-service

The directory the whole company runs on.

Join once, and every app already knows who you are and what you can see.

Get started → See pricing