Manage people
One record per person. Everything on file.
Personal details, documents, contracts, salary history, transfers, warnings, exits — a single employee record that accumulates history instead of overwriting it.
01 · The timeline
One record. Two years. Nothing overwritten.
This is Ananya’s record, from her first day to her last payslip. Drag the scrubber — or arrow-key through it — and watch the history accrue: documents to nine, two salary revisions, every event dated and attributed. The record only ever grows.
31 Mar 2026 · payroll
March run · paid
Paid at the new basic; January–February recomputed and posted as a ₹12,000 arrear line.
recorded by Payroll · admin
- on file
- 9 documents
- basic in force
- ₹48,000
- record
- append-only
Every stop is an appended event with an actor and a date — the way the product records lifecycle, documents and revisions. Nothing above overwrites anything before it.
Single source of truth
Payroll, attendance, and performance read this record. There is no second copy to drift.
History, not overwrites
Promotions, transfers, and revisions append to the record — the past stays visible.
Documents that acknowledge
Policies and letters carry acknowledgment tracking, so “I never saw it” has an answer.
The capabilities, in detail.
Personal, job, bank, and statutory identifiers in one structured profile with field-level access control.
- Structured profiles with role-scoped visibility
- Branch, department, and designation mapping
- Statutory identifiers stored once, used everywhere
Quick answer
Who can see what on a record?
Permissions go to field level — an approver can see what they approve, and nothing else.
See it on your own questions.
A 30-minute demo, tailored to your states, your policies, and your payroll. No obligation.
