Product features: Human Resources (app)
with a workspace selected, open Human Resources on the apps desktop to maintain this workspace’s org, people, recruiting, and development. Aimed at R&D service companies; factory f
Source help/en/product-features/platform-hr.md
In user language: with a workspace selected, open Human Resources on the apps desktop to maintain this workspace’s org, people, recruiting, and development. Aimed at R&D service companies; factory floor should use Manufacturing HR.
Related: Use the action assistant for Human Resources · How permissions work · Workspace apps
Chat as action
Tell the app assistant in Human Resources what you want, e.g. “list departments”, “add a test group under R&D”, “register Zhang San’s hire”. It acts within your permissions; you do not have to memorize tabs. Only “how do I open the org chart” gets a page explanation.
If New hire ticket is already open, telling the app assistant name, ID, department, and similar writes into this draft and shows immediately; you confirm then tap Create ticket. Do not assume speaking it has already hired them onto the roster.
The same kind of request to the help agent in another module uses the same operations.
What you can do
| Capability | What you get | One-tap open (only when you are already inside Human Resources) |
|---|---|---|
| Org chart | Department tree; add/adjust departments; history | Open org chart |
| People and org | Roster vs departments; records include ID, photos, emergency contacts, and whether hire materials are complete | Open People and org |
| Hire / leave / transfer | Register hire, leave, transfer | Open hire/leave/transfer |
| Settings | After hire/leave/transfer completes, auto-start a workflow; recruiting linked by stage; extra form fields per company | Open settings |
| Jobs and levels | Tracks, grades, jobs; job families from a catalog. Headcount per track and grade. Open a job to write duties and qualifications (Add qualifications if none), compare incumbents’ level standards. Unopened grades are hidden until you enable them; you can disable a grade with nobody attached | Open jobs and levels |
| Competency standards | Capability items and level behaviors; job-family and specialty booklets; admins can disable/delete unused items | Open competency standards |
| Succession | Succession benches | Open succession |
| Growth profile | Personal development comparison (demo is not formal performance) | Open growth profile |
| Recruiting | Hiring jobs from approved staffing requests (to hire more, submit another staffing request; sources are listed on the job), resumes (batch PDF/Word/web; the model extracts fields vs the request; unmatched people can be matched all / several / one at a time; previewable), multi-round interviews and online tests, Offer; draft from headcount gaps. Interviews can include side questions, recording, and scores. After hire, still go through hire/leave/transfer | Open headcount requests |
| Overview | Size snapshot | Open Human Resources overview |
Or open the desktop first: Go to apps desktop → Human Resources. After open, hover or click the top-left mark to switch groups such as Recruiting, Performance, Settings. If the user is not currently in Human Resources, describe the entry in words — do not copy the deep links above.
How to open
- Select a workspace in the top bar
- Click a link in the table, or Apps → Human Resources
The first time an admin opens it, plugin notes sync to workspace knowledge so assistants understand this module.
Kickoff survey and setup guide
When Human Resources has no HR data yet, a workspace admin can fill a kickoff survey on Overview. The system generates a common org, levels, jobs, and competency skeleton, then walks you through completing it. Workspaces that already have data do not repeat kickoff. You can skip the survey with “use demo data” (empty database only).
Org chart (highlights)
- To add or adjust a department: tell the app assistant first, e.g. “add a child department Test group under R&D”. Code can be empty; the system generates from the name.
- You can also work on the canvas: connector diagram or tree list; zoom the diagram. Department nodes mainly show name and headcount. Admins hovering a department can edit or add a child.
- To keep a record, tell the app assistant “save the current org as a history snapshot”, or save a history snapshot on the page (read-only).
Members vs employees
- Workspace members: can collaborate in this workspace and open this app.
- Employees: people in the HR roster.
- They need not be one account each; inviting someone into the workspace is not an automatic hire.
Auto-start workflow after hire/leave/transfer completes
HR specialists or admins switch to Settings (top left; no longer in the HR sidebar) and configure separately for hire / leave / transfer and recruiting hooks:
- Whether completing that ticket auto-starts a Cadau workflow
- Which published process definition (hire often uses the “Employee onboarding” template)
- Optional default handler (hire side often warehouse; written into the flow for “form variable” assignees)
Entry: Open settings (already inside Human Resources). Recruiting hooks: Open recruiting flow hooks. Extra fields per company: Form fields; built-in fields cannot be deleted.
Parameters auto-filled when a flow starts (process variables)
After complete-and-start succeeds, these write into the instance variable table for later form fill (same-name prefills), assignee → form variable, {{variable}} in agent work · task notes, and writing back app-work results.
| Variable | Meaning | Hire | Leave | Transfer |
|---|---|---|---|---|
employee_id | Employee primary key | ✓ | ✓ | ✓ |
emp_no | Employee number | ✓ | ✓ | ✓ |
display_name | Display name | ✓ | ✓ | ✓ |
org_unit_id | Org unit | ✓ | ✓ | ✓ |
mobile | Mobile | ✓ | ✓ | ✓ |
email | ✓ | ✓ | ✓ | |
hire_date | Hire date | ✓ | ✓ | ✓ |
leave_date | Leave date (often empty on hire) | ✓ | ✓ | ✓ |
lifecycle_case_id | This hire/leave/transfer ticket | ✓ | ✓ | ✓ |
lifecycle_kind | Kind: onboarding / offboarding / transfer | ✓ | ✓ | ✓ |
handler_user_id | Handler from Settings (omitted if none) | optional | optional | optional |
warehouse_user_id | Same as handler (warehouse nodes) | optional | — | — |
How to use (config side)
- Assignee type form variable, fill
handler_user_idorwarehouse_user_id(handler must be set in Settings). - Agent task note example:
Handle follow-up for employee {{display_name}} (emp no {{emp_no}}). - Keys written back when app work completes (e.g. account-bind result) come from the node’s result variables, not this table.
How to check after it runs
Open Workflow → that instance; full key/values are in the instance payload variable table (the UI may show only some fields). Finer node in/out variables: Process designer guide (for configurators; the help agent usually need not copy implementation paths).
Permissions
- Workspace members: mainly view; if the employee record is bound to their account, they can fill their own self-review.
- Line manager (direct supervisor on the record or a designated reviewer, with a bound account): can fill and submit manager review for reports.
- HR specialist (appointed by a workspace admin on Human Resources overview): can maintain org and people, review cycles, etc., with the same write rights as admins inside this app.
- Calibrator: can write the effective band in the calibration stage.
- Workspace admin / creator: all write rights; can appoint HR specialists and calibrators; can bind a Cadau account on a people record.
Steps: How permissions work.
Phrases and permissions: Use the action assistant for Human Resources.