Appearance
Document Collection & Employee Verification (HCM)
This page documents two shipped Onboarding screens (hcm-onboarding). Not for plugin developers.
Document Collection
Request a document from a new joiner. Uploads are real — the file lands in your tenant's document storage (a real "HCM Onboarding Documents" folder, created automatically) — not a placeholder. From a document's detail view: Verify, Reject, Request Resubmission, Waive, Cancel, or Download, each recorded in a real history log.
There's no document versioning — re-uploading a file replaces it in place, it doesn't keep the old version alongside the new one.
Employee Verification
Open a verification case for a new joiner, then add individual checks underneath it (e.g. Identity, Employment). For each check, Record Decision — status, result, a failure reason if it didn't pass, who reviewed it, and comments. As you decide checks, the case's own overall progress % and result are recalculated automatically — you don't total it up yourself.
Known gaps
- Verification is single-reviewer — the original design describes a multi-party Reviewer → HR Manager → Compliance chain for high-risk checks, but that isn't built; one person's decision closes a check.
- No versioning on documents — see above.
- A check's supporting evidence is a freeform reference, not formally linked to Document Collection, even though you can point it at a document by typing a reference to it.
