Implementing Global HR: From Enterprise Model to Live Workforce · Module 2 · Security and Role Provisioning
Why HCM security is different
Lesson 12 of 175 · 5 min
If you have done a Financials implementation, you have a security model in your head. Put it down for the next hour and a half. HCM security is not a variation on that model. It is a different model — and assuming otherwise is the fastest route to a broken configuration, because the pieces have familiar names and behave differently. What is the same is short: function security. User, to role, to duty, to privilege — what you can do, which pages open and which buttons work. That mechanism is shared across the product family and you already know it. What is not is data security. In most applications "which rows can I see" is answered by an organisational scope like a ledger or a business unit. In HCM, "which rows" means "which people" — and you cannot answer that with a simple scope, because the real requirements are not…
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