Leave & requests
Emergency leave, annual leave, and other requests each carry their own fields and approval route.
People · HR & People
People operations that route themselves.
Leave, payroll, hiring, and employee records in one place — every request following the right approval path for its type and department, with the conversation and the decision attached to the person it concerns.
Per-typerouting for every request
One recordper person, end to end
Built-inchat on every case
Drag to rotate
Illustrative interface — leave and hiring requests routed by type and department.
What makes it different
HR without the email chains.
Payroll-ready records
Keep structured employee data that feeds payroll, with company and department context.
Hiring & intake
Capture applicants and structured intake, moving candidates through a clear pipeline.
Department routing
Approval routes send each request to the right primary and fallback approver with an SLA.
Employee records
Roles, permissions, company, and onboarding status live on one governed profile.
Case conversations
Discuss a request in context — the thread stays attached to the person and the decision.
Separate HR software vs Prime RP
| Capability | Standalone HR tools | Prime RP |
|---|---|---|
| Per-request-type routing | Configurable | Built-in |
| Shares roles with the ERP | Separate | Unified |
| Chat tied to the case | No | Yes |
| Approvals engine reused | No | Yes |
| One record across modules | No | Yes |
FAQ
Questions, answered
Yes — approval routes are defined per request type and department, each with primary and fallback approvers and an SLA.
Yes. People, roles, and permissions are the same records the whole platform uses, so there's no duplicate directory to maintain.
Yes — HR requests run through the same approval engine, so every decision is timestamped and attributed.
Give HR a system, not an inbox.
See a leave request route, approve, and file itself in minutes.