People · HR & People
One employee record, and everything that hangs off it.
Included from Starter upward.
The org chart lives in a slide, the salary in a spreadsheet, the reporting line in somebody's head. When a person moves teams, four systems disagree about who approves their leave.
What it does
The record every other module reads.
- 01
People and the reporting line
Departments, designations and managers, stored as a real hierarchy rather than a text field — which is what lets a manager's scope mean 'my reports and theirs'.
- 02
Hiring and applications
Openings, candidates and their stage, with candidates able to hold a portal account that reaches their own application and nothing else.
- 03
Learning
Courses assigned to people, with completion tracked against the same employee record payroll reads.
- 04
Joining and leaving
An exit disables the account and keeps the history. The row stays for the audit trail and stops consuming a seat.
For example
Devika joins on the 3rd, and four modules already know
- 1HR creates one record: Devika Rao, Delivery, reporting to the Delivery Head.
- 2That reporting line is not a label — it is what makes her manager's scope mean “my reports and theirs”.
- 3Attendance opens her leave balances the same day: 12 casual, 12 sick, 18 earned.
- 4Payroll picks her up in the March run without anybody adding her to it.
- 5She is assigned to P-ACME, so her hours can be booked and billed.
One record entered once. Nobody re-keys her into a second system, and no system disagrees about who approves her leave.
How it runs
In, through, out
A person is hired
Their record, line and access are set once
Attendance, payroll, projects and reports all read it
The reporting line is not documentation here — it is the thing that decides whose leave you can approve and whose salary you cannot see.
In the product
Actual screens, not mockups
It does not work alone
What HR & People is connected to
The point of one set of records is that these are not integrations. They read the same rows.
Problems it solves