Every screen
Every screen in PeopleNest has a page here. They are grouped by module, and inside a module they are in the order you would meet them setting it up: the setup screens first, the daily screens next, the period end screens last.
If you know the screen's name, use the search box. If you know the problem but not the screen, start at How do I… instead.
The modules
Shared by everything
Organization & Setup
The company itself: the legal entity, the units, the departments, the calendar, the shift times, the approval chains, and the small code lists that half the other screens borrow from. Fill these first or the rest of the system has nothing to point at.
The people
People Directory
Positions and grades, then the employee record and everything held against a person: addresses, identification, education, skills, the organization assignment that places them in the company, and the policy profile that decides which rules calculate their pay and leave.
Days and hours
Time Management
Shift patterns and rosters, the attendance policy that decides what a punch means, the machines that collect the punches, leave in all its forms, overtime, and the attendance sheet that turns a month of all that into numbers payroll can pay.
Money
Payroll
Wage types and what each one does to net pay, pay scales, pay periods, tax slabs, contributions and the provident fund, loans, the payroll run itself, posting, and the final settlement.
Appraisal
Performance
Goals and metrics, the appraisal form, who belongs to which appraisal population, the evaluation cycle and its windows, scoring, calibration, and the increment matrix.
Learning
Training
Courses, trainers and vendors, the training need that becomes a plan that becomes a schedule, attendance, assessment, feedback, and bonds.
Hiring
Recruitment & Onboarding
The requisition, the public careers page, the applicant, screening, interview scoring, the offer, and the walk from an accepted offer to an employee record.
How to read a screen page
Every one is built the same way. What it is for says why the screen exists and what goes wrong without it. Every field, in plain words gives a row per field, with a value you could actually type and every code the field accepts. How to configure it is a numbered walk from an empty screen to a saved record. Scenarios shows the same screen set up two ways for two different clients. What it is connected to says what must exist first and what reads it afterwards. If something looks wrong lists the symptom a client would report and the first thing to check.
The codes a field accepts are also collected in one place, in Words & values, if you would rather look them up than hunt for the screen.