User and role provisioning

What happens automatically when somebody is hired, and what happens when they leave. Get this right and the client will notice, because it is the difference between an HR team that files an IT ticket for every hire and one that does not. The setup options first: when accounts are created — on hire, or by a separate process; where the user name comes from — email address, person number, something else; and whether accounts are created automatically at all. Pause on the user name format, because it is effectively permanent. Once accounts exist, changing it means changing every user name — every integration that references them, every saved credential, and a communication to the whole workforce. Decide it with the client's IT team, in writing, before you create the first account. It is a five-minute decision that is very expensive to revisit, and IT will have an opinion because…

In this module: Module 2 · Security and Role Provisioning

1. 1Why HCM security is different
2. 2Security profiles: the six types
3. 3Building person security profiles
4. 4Organization, position and LDG profiles
5. 5HCM data roles
6. 6Areas of responsibility
7. 7User and role provisioning
8. 8Data protection by design
9. 9What breaksFree preview
10. 10Lab: build the security model for four countries