Person types

System person types are fixed and drive behaviour: employee, contingent worker, non-worker, pending worker. User person types sit underneath them and are yours to define — "Intern", "Fixed-term Employee", "Board Member". Why user person types matter: reporting, eligibility, security criteria and process routing all key off them. Four consumers, which is why the design guidance is tighter than it looks. Pending worker is the pre-hire state, and its role in onboarding and the recruiting handoff is worth explaining properly — many implementations underuse it and then invent something worse. Non-worker is for people who need records without employment: volunteers, retirees, beneficiaries. And the design guidance: create user person types you will actually report on or restrict by. Not one per contract variant. The instinct is to model every distinction HR mentions; the test is whether anything downstream keys off it. Then the build: create user person types under two system…

In this module: Module 9 · Person

1. 1The person record and effective datingFree preview
2. 2Person number generation
3. 3Person types
4. 4Name styles and formats
5. 5National identifiers and addresses
6. 6Demographic information and lookups
7. 7Person search and keywords
8. 8Photos, duplicates and record synchronization
9. 9Batch loading workers
10. 10What breaks
11. 11Lab: configure the person record and load 200 workers