Lab: design the joiner-mover-leaver integrations

Thirty minutes, and most of it is writing rather than clicking. Connections configured, with documented data protection decisions. Help Desk configured, with agent access scoped via a Module 2 security profile — scoped, not global, which is the fifth failure. A written joiner-mover-leaver integration design: for three named downstream consumers, the pattern, the data set, the latency, the failure handling and the named owner. Five things per consumer, and the last two are the ones that get left blank — which is exactly where the unowned-monitoring and day-one-access failures come from. And a note on payload minimisation for each. Three acceptance criteria, and each maps to a failure. Each integration names the minimum data set required, not the full record. Each has a named monitoring owner — a name, not a team. And Help Desk agent access is scoped, not global. That is the last module before the capstone. Everything…

In this module: Module 17 · Connections, Help Desk and Integration

1. 1Connections
2. 2HR Help Desk configuration
3. 3Publishing person and assignment changes
4. 4Integration patterns for workforce data
5. 5What breaks
6. 6Lab: design the joiner-mover-leaver integrations