The decision that does not feel like one

THE ONLY FLAGSHIP IN THIS COURSE WHERE THE WRONG DECISION DOES NOT FEEL LIKE A DECISION AT ALL. Nobody chooses per-user assignment. They just start. And then they have five hundred users. Five environments. Five hundred users. An average of two roles each. Five thousand grants. Every joiner is ten actions. Every leaver is ten actions — all of which must happen, none of which anyone will verify. What the group model does instead. Roles are assigned to groups. People are added to groups. A joiner is one action. A leaver is one action. And an access review reads a group membership list rather than five thousand grants. Why retrofitting is expensive. You cannot simply switch. You must map existing grants, design the groups, assign roles to them, add members, verify equivalence, then remove the individual grants. On a live estate that is weeks, and it needs a security sign-off.…

In this module: Module 6 · Users, Groups and the Role Model

1. 1What we are building
2. 2The decision that does not feel like oneFree preview
3. 3The access object model
4. 4Predefined application roles
5. 5Roles by business process
6. 6Domain-level administrator roles
7. 7Designing the group model
8. 8Creating users
9. 9Creating groups
10. 10Policies for users and groups
11. 11Assigning roles to groups
12. 12Unassigning and offboarding
13. 13Proving the model works
14. 14What breaks
15. 15Lab briefing: a role model for eight environments
16. 16Lab solution walkthrough