People

People is the HR module: personnel records, the organisation structure, HR documents, change requests, onboarding and offboarding, and HR reports. It owns who somebody is and how they are employed. Absences, vacation, sickness and time balances belong to Time; People shows what Time knows on each record but does not keep a second copy.

Where to find itCopy Anchor Link

Open People from your pinned apps or All apps, or press ⌘K and type the page you want (employees, onboarding, people requests). The People sidebar has four groups. You only see the entries your role reaches; a group with nothing you may open is not shown.

The counts on the sidebar are things waiting on you: your inbox on Me, expiring documents, open onboarding and offboarding, and pending requests. The head count and FTE at the bottom of the sidebar link to Reports.

The employee lifecycleCopy Anchor Link

A record moves through these states: draft → preboarding → active → (leave of absence) → offboarding → inactive → archived. The order of the In progress group follows the same path: onboarding, then requests during employment, then offboarding.

1. Hire somebody and start their onboardingCopy Anchor Link

12345

1. 1Add somebodyOpens a new employee record.
2. 2First nameFirst and last name are all a record needs. The personnel number is allocated.
3. 3Starts onOptional. Onboarding is dated from it, or from today without one.
4. 4Start onboardingLeave it on to run the matching onboarding template.
5. 5CreateThe new record opens, ready for its employment period.

1. Go to People → Employees and select Add somebody.
2. Enter first and last name. Work email, start date and a linked account are optional; the personnel number is allocated automatically. The record starts in preboarding.
3. Leave Start onboarding on (shown only if you may manage onboarding). The matching onboarding template runs, dated from the start date, or from today if no start date is set.
4. Select Create. The new record opens so you can add the employment period (department, position, hours) on the Employment tab.

If onboarding cannot be started, the record is still created and a message tells you to start the workflow from the record.

2. Start a workflow from the boardCopy Anchor Link

12345

1. 1Start onboardingIn the header, and on an empty board.
2. 2EmployeeWho the workflow is for.
3. 3Anchor dateThe day the steps are dated from.
4. 4TemplateOptional. Left to match, the most specific fitting template runs.
5. 5Start itStarts the workflow.

1. Go to People → Onboarding (or Offboarding) and select Start onboarding (or Start offboarding) in the header. The same button appears on an empty board.
2. Choose the employee, the kind, the anchor date (the day the steps are dated from) and optionally a template. Without a template, the most specific template whose conditions fit the person's department and position runs.
3. Select Start it.

You can also start any workflow (onboarding, offboarding, transfer, probation) from a person's record with Start a workflow in the record header.

3. Work through onboarding and offboardingCopy Anchor Link

12345

1. 1StateFilters the board by state.
2. 2DepartmentShows one department’s new starters.
3. 3Past its dateGrouped by anchor date: past its date, within the week, later and finished.
4. 4StepsA card’s steps, opened from its count of steps left.
5. 5Run itRuns a step that reaches into another module, here inviting an account.

The board groups workflows by their anchor date: Past its date, Within the week, Later and Finished. Filter by state and department in the toolbar. Open a card to see its steps. Steps can reach into other modules — invite an account, add somebody to a team, open a board item, set a working week in Time — and each step links to what it touched. A failed step says why and does not stop the others; fix the cause and run it again, or skip it.

4. Handle change requestsCopy Anchor Link

12345

1. 1Waiting for a decisionChange requests waiting for you. Decided ones stay listed under Decided.
2. 2The proposed changeWhat the record says now against what the person asks for.
3. 3WhyA comment, required to reject and read by the person either way.
4. 4ApproveApplies the change to the record.
5. 5RejectTurns the request down. It needs a comment first.

Employees ask for changes from Me → Ask for a change (contact details or name). The button is there only when your role lets you ask (hr.self.change.request). A request goes to the person's manager first, and to HR when there is no manager of record. Nothing changes until somebody approves it.

Approvers open People → Requests, read the proposed change against what the record says now, and approve or reject with a comment. Decided requests stay listed under Decided.

Leave, vacation and sickness are not People requests: they are requested and approved in Time. The Time panel on a record shows the person's availability and balances and links to Time: the approval badges open Approvals narrowed to that person, and your own record's unsubmitted-entries badge opens Project time.

5. Record a leaving date and offboardCopy Anchor Link

12345

1. 1EmploymentThe tab with the person’s employment history.
2. 2Record a leaving dateEnds the employment and nothing else. No record is deleted.
3. 3Last dayThe last day worked.
4. 4ReasonWhy the employment ends.
5. 5Start a workflowStarts the offboarding for the handover.

1. Open the person's record, Employment tab, and record the leaving date and reason. This ends the employment and nothing else; no record is deleted.
2. Start an offboarding workflow (from the record header or People → Offboarding) for the handover. Deactivating the account is a step of the offboarding workflow.
3. Move the record's state (to inactive, later archived) with Move this record when the handover is complete. Archiving is blocked while a legal hold covers the record.

Finding and managing recordsCopy Anchor Link

12345

1. 1SearchName, personnel number or work email, searched on the server.
2. 2StateFilters by the record’s state.
3. 3DepartmentFilters by department; Position works the same way.
4. 4As atReads the directory as it stood on a given day.
5. 5Table / CardsSwitches between the table and cards.

• Employees searches by name, personnel number and work email on the server, and filters by state, department, position and an "as at" date. Switch between table and cards in the header.
• Documents searches title, category, person and file name, and filters by category, person, state and expiry (expired, expiring within 30 days).
• When a search or filter leaves either list empty, Clear filters in the empty list resets them all at once.
• A record has tabs for Overview, Employment, Contact, Documents, Pay, Notes and History. Pay and notes appear only for roles that may read them.
• Every date in People — start, probation end, leaving date, employment periods, document issue and expiry, workflow steps and legal holds — is written in your language, not as 2026-08-17.

OrganisationCopy Anchor Link

1234

1. 1ChartThe units, with their people and vacancies. Select one to see it beside the chart.
2. 2AddCreates something new in the structure.
3. 3Add to the organisationA unit, a position, a location or a cost centre.
4. 4ArchiveArchived items stay on file and can be restored.

People → Organisation holds the structure: units (company, division, department, team, group), positions, locations with their time zone, and cost centres. Use Add to the organisation to create one. Archived items stay on file and can be restored.

ReportsCopy Anchor Link

1234

1. 1The thirteen reportsIn four groups: who is here, what is coming, what needs doing and how it is put together.
2. 2Employee directoryA report marked file can be exported; the others are screens.
3. 3Export as CSVExports the open report as a file.
4. 4Requests waitingOverview tiles open the open onboarding, offboarding and requests.

People → Reports has thirteen reports in four groups: Who is here, What is coming, What needs doing and How it is put together. Five of them (directory, headcount, joiners and leavers, documents, org chart) can be exported as a file; the rest are screens. Overview tiles link to the open onboarding, offboarding and requests.

Roles and permissionsCopy Anchor Link

Permissions are granted on the console's roles screen, System console → Access → Roles (/admin/access/roles, tier Modules), not inside People. The People sidebar shows an entry only when you hold one of the permissions it needs:

hr.team.* permissions cover a manager's own reports; the others cover the whole organisation. Everybody sees Me; it never shows pay, private notes or termination details about yourself.

AdministrationCopy Anchor Link

1234

1. 1Open rolesPeople permissions are granted in the system console’s roles screen.
2. 2Define a fieldA custom field with its type, visibility and retention.
3. 3New templateThe steps of an onboarding or offboarding, and who it matches.
4. 4Place a holdA legal hold outranks every retention rule and erasure.

People → Administration (/people/admin) holds:

• Custom fields — extra fields on the record, each with a type, a visibility (HR only, employee and HR, manager and HR, everyone, sensitive, health and HR) and a retention rule.
• Workflow templates — the steps of an onboarding or offboarding, and the department, position and contract type they match.
• Legal holds — a hold outranks every retention rule and erasure for the records it covers.

The old address /people/admin/permissions redirects here. The module itself is installed and switched on in System console → Marketplace → People.

TipsCopy Anchor Link

• Create the record, start onboarding and fill in the employment period in one sitting: the new record opens right after creation.
• Filter the onboarding board by department to see one team's new starters.
• A department filter on a board reads the first 200 people of that department; a note appears when the department is larger.
• Use Reports to export the directory or headcount rather than copying tables.