These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- HRMS with Employee Self-Service
- Features
- Employee records
Employee records
Keep the employee roster and lifecycle history tied to positions and departments.
OverviewOnboarding work×
HRMS with Employee Self-Service · Employee records
New
Onboarding work
Onboarding tasks
IT1
Pending ot-760OC-63547
13 Oct
Add
Facilities1
In progress ot-642OC-30085
25 Oct
Add
Payroll1
Blocked ot-864OC-27582
07 Oct
Add
HR1
Pending ot-241OC-92574
19 Oct
Add
Compliance1
In progress ot-754OC-23637
13 Oct
Add
What you can do
Keep the work anchored to a person
The staff roster begins with the employee record. HR Business Partner (HRBP) checks the person, position, department and location before using it in leave, pay or service work. The Employee Directory gives HR an administrative roster that can be searched and filtered by current employment status. A row opens the native employee record for the detailed history.
For a transfer, HR records an employment history event with its effective date, prior and new position, and prior and new manager where relevant. HR updates the current employee assignment alongside the dated history. The history remains useful when a later pay statement or request needs to be understood in the context of the person’s earlier assignment.
How the work is organized
- Check the source. HR Business Partner (HRBP) checks employee identity, department, position, manager and location before recording a dated lifecycle event. The Employee Directory opens the native employee record for detail.
- Record the decision. A transfer, manager change or separation has an effective date and a recorded person. Keep the prior position or manager on the history event so current and earlier assignments can be distinguished.
- Keep the trail. A later correction should preserve the dated event and its recorder. Confirm the employee reference before another team uses it for leave, pay or onboarding.
What to agree during setup
Agree who can maintain employees and positions, which organization owns each person, and how the team records an effective transfer or separation. Confirm employee identifiers, work email, manager and location before importing current staff. Review the roster with HR before other teams begin using its references.
Open the Employee Directory, filter to the person and inspect their native record. Trace a mid-period transfer through its employment history and compare the current department and manager with the prior event.
Check the handoff on an actual case
Take one employee who moves departments mid-period. Open their directory row, check the current position and manager, then locate the event that records the change and its effective date. Follow a leave request and a pay statement to the same employee. HR should be able to explain which record shows the current assignment and which one preserves the earlier state.
Have the next person find the same employee and period, explain the current status, and identify the source detail behind it. Correct a mismatched reference before the case moves forward.
What your team sees
- Employee Directory — HR searches the roster by name, status, department or location and opens the employee record.
- Onboarding work — HR can check tasks attached to a newly hired employee.
Follow the work through
See leave approval for a decision tied to the employee record.
What it keeps track of
Data model- Employees
- The central person record. Every transaction in the suite ties back to Employees.
- Departments
- Organizational departments.
- Positions
- Seat-level org entries. A position is what an employee fills.
- Job titles
- Canonical job titles.
- Locations
- Physical and remote locations where employees work.
- Employment history
- Every lifecycle event: hire, promotion, transfer, comp change, manager change, leave of absence, termination.
- Organizations
- Legal and business organizations that own employment relationships.
Who uses it
Permissions- HR Business Partner
- (HRBP) maintains employee and lifecycle records.
- Recruiter
- And Hiring Manager read the permitted person and position context.
Set up HRMS with Employee Self-Service your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.