Loading
Because every system needs its own copy of the same person. A joiner is entered into HR, payroll, the delivery tool and the help desk, by hand, four times.
A leaver is worse: they are removed from whichever ones somebody remembers, and are still in the directory eight months later.
There is one personnel record. Payroll reads it, capacity planning in Loop reads it, access requests in Desk read it, and Books posts its cost.
A joiner exists once; a leaver is closed once and disappears from everything that was reading them.
It will not make policy decisions. It enforces the rules you configure and records exceptions; the judgement stays with people.
It also will not grant system access — it raises the request with the right approver.
The administrative half of the job shrinks, and the half that matters — policy, cases, development — gets the time.
Audit questions become answerable. Who reported to whom in March, when a policy was acknowledged, what changed and who approved it are all on the record.
Products, not integrations. Each one reads the same record, so a join is a permission rather than a sync job with a mapping screen behind it.
Yes, with separate statutory settings per entity.
On the fields you permit; role and reporting line never.
Kept with effective dates, which is what audits ask for.
Half an hour on your own numbers is usually enough to say whether Nest is the right place to start.