Beta · guided availability
Employee directory & hierarchy
Keep departments, locations, reporting relationships and employment history together. Company membership is explicit—not inferred from a matching email domain.
Beta · guided availability
Run internal people operations around a verified employee identity: joining, directory, attendance, leave, documents, performance and assigned assets. Keep sensitive compensation and identity information behind their own permissions.
Your own employees. A clearer operational record.
The lifecycle
Step 1
Requisitions, jobs, candidates, interviews, offers and preboarding through internal HRMS Hiring.
Step 2
Task templates, induction content and a case per joiner so nothing is left to memory.
Step 3
Attendance, leave, timesheets, payroll, expenses, performance, learning and helpdesk in one place.
Step 4
Resignation, clearances, final settlement and issued letters, all recorded against the person.
Inside People
Employees with departments, locations, designations, grades and employment types, plus an org chart and full change history.
External staffing is a separate product; placed workers do not become internal employees.
Learn moreShifts, rosters, holidays, leave types and balances, with approvals and regularisation.
Salary structures, payroll runs, payslips and expense claims, with compensation visible only to those permitted.
Goals, review cycles, feedback, courses and enrolments.
Issued letters, personal documents and compliance registers, with identity documents separately gated.
HR tickets, announcements, surveys and recognition.
Live workforce, leave, payroll and compliance reporting with every export logged.
Handled carefully
Salary, bank accounts and identity documents sit behind separate permissions from the general employee record — being an HR user is not the same as being allowed to see pay.
Role changes, salary edits, document downloads and exports are recorded with who did them and when.
Questions
Yes. People is enabled per workspace, and internal hiring remains separate from external staffing ATS.
Only people granted the compensation permission. General HR access does not include it.
Yes. Access and People are separate families on the same platform, with the same sign-in, tenant isolation and audit.
We will show how the same records look once hiring, the employee file and approvals live in one place.
The workflow
Identify the actual employee and approved employment.
Collect private details and complete joining tasks.
Review attendance, leave, assets and performance in context.
Preserve employment and document history when responsibilities change.
Inside the product
Beta · guided availability
Keep departments, locations, reporting relationships and employment history together. Company membership is explicit—not inferred from a matching email domain.
Beta · guided availability
Review internal joining records, collect personal information and private documents, and track the tasks needed for a new employee.
Beta · guided availability
Manage shifts, calendars, attendance exceptions and regularization in the employee workflow. Device activity does not become attendance automatically.
Beta · guided availability
Handle leave requests and approvals with policy and calendar context. Private leave information does not become public recruiter-performance detail.
Beta · guided availability
Review goals and effective-dated reporting context. Performance Intelligence has separate scoring and release gates; missing metrics remain Missing or Unverified.
Beta · guided availability
Track assigned equipment and employee files with scoped access. Keep historical records when an assignment or employment status changes.
Beta · guided availability
General HR access is not salary, banking or identity-document access. Payroll and compensation remain separately permissioned and MFA-protected.
Pilot · not generally available
Reviewed internal employee inputs support the separate India-first Payroll pilot—not external staffing payroll.
Availability & boundaries
People is for the company’s internal employees. A clinician placed through ATS does not automatically become an HRMS employee. Broad workflow coverage exists in source; company setup and authenticated acceptance remain required.
One platform, separate responsibilities
Client systems
Assigned destinations and credential-controlled launches.
External staffing
Candidate pipelines, placement readiness and approved economics.
Internal employees
Employment records, controlled payroll pilot and visible activity pilot.
A shared platform does not merge records or authority. Staffing placements never automatically become employees; Work activity never automatically becomes attendance or pay.
Start with your operation
Show us the client systems, staffing process or internal people workflow you want to improve. We’ll discuss fit, availability and the steps to a controlled rollout.