One employee record
Permissions, attendance, and pay share the same people directory.
Solutions / HRMS Suite
People ops. Same org graph.
Staff runs hire-to-pay workflows; Forms turns onboarding and audits into structured data — on the same identity model as the rest of Vipani.
- One employee identity
- Approvals that leave a trail
- Forms instead of paper
From directory to daily capture.
People data that projects, permissions, and field forms can reuse.
Staff
Forms
Tasks
Projects
Why HRMS Suite
HR that stays useful beyond HR.
Approvals in the flow
Leave, claims, advances, and geo exceptions with clear trails.
Structured field capture
Forms builder with public links — not WhatsApp photo threads.
What people teams run
Directory, time, pay, and forms — connected.
Less chase for timesheets. Clearer claims. Cleaner data.
Employee directory
Import, invite, provision Vipani accounts, roles.
Attendance & geo
HR and employee views, geo-fence approvals, trail maps.
Leaves & payroll
Leave ledger, holidays, payslips, advances.
Claims & reimbursements
Bills and advances with approval paths.
Form builder
Sections, visibility rules, cascading fields, templates.
Submissions inbox
Detail views, export, PDF — including public response URLs.
Included miniapps
Staff and Forms — with delivery context nearby.
Staff
- Employees, attendance, geo-tracking
- Leaves, payroll, payslips, advances
- Claims, letters, policies, daily reports
Forms
- Visual form builder and field library
- Public response URLs
- Submissions inbox with PDF export
Tasks
- Boards for people-driven work
- Assignees and hours
- Useful next to Staff and Projects
Projects
- Staff projects against delivery
- Teams and timesheets
- Connects people ops to outcomes
Hire→Pay
Staff workflows
Geo
Attendance & trails
Forms
Structured capture
1
Org identity model
Ready for people ops on one graph?