Implementing Global HR: From Enterprise Model to Live Workforce · Module 2 · Security and Role Provisioning
Areas of responsibility
Lesson 17 of 175 · 14 min
This lesson is a design pattern, and it is the one to adopt as a default. An area of responsibility says: this person is the HR representative for that population. It does two jobs — it routes, sending transactions and notifications to the right person, and it can drive security, because a person security profile can be built from it. You can scope one by legal employer, business unit, department, country, position, grade, and combinations, so "the HR advisor for the UK legal employer" is directly expressible. Here is why it beats hard-coding, shown with the thing that actually happens: the Germany HR advisor leaves and somebody else takes over. In the hard-coded design, the data role was built with a profile scoped to Germany and assigned to that person, so you unassign it, assign it to the new person, check their other roles, regenerate and test — and if…
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Implementing Global HR: From Enterprise Model to Live Workforce, with a certificate on completion and a fourteen-day refund window.
In this module: Module 2 · Security and Role Provisioning
- 1Why HCM security is different
- 2Security profiles: the six types
- 3Building person security profiles
- 4Organization, position and LDG profiles
- 5HCM data roles
- 6Areas of responsibility
- 7User and role provisioning
- 8Data protection by design
- 9What breaksFree preview
- 10Lab: build the security model for four countries