Administering Cloud EPM: The Platform Beneath the Business Processes · Module 6 · Users, Groups and the Role Model
Unassigning and offboarding
Lesson 73 of 201 · 11 min
Remove a user from a group and show access disappearing. Unassign a role from a group. Deactivate a user. Delete a user, and when you would and would not. Then the offboarding checklist: group memberships, domain administration, console access, client credentials, scheduled automation running under their account. OFFBOARDING IS WHERE PER-USER ASSIGNMENT KILLS YOU AND GROUP ASSIGNMENT SAVES YOU. One removal versus ten — and only one of those is reliably completed. THE AUTOMATION QUESTION IS THE ONE PEOPLE MISS. If a leaver's account is running scheduled EPM Automate jobs, deleting them breaks the jobs SILENTLY. Module 11 covers service accounts; the dependency is flagged here. Deactivate before deleting where you can. Deletion is irreversible and occasionally premature.
The full lesson is part of the course
The video, the complete written lesson and the module quiz are included in Administering Cloud EPM: The Platform Beneath the Business Processes, with a certificate on completion and a fourteen-day refund window.
In this module: Module 6 · Users, Groups and the Role Model
- 1What we are building
- 2The decision that does not feel like oneFree preview
- 3The access object model
- 4Predefined application roles
- 5Roles by business process
- 6Domain-level administrator roles
- 7Designing the group model
- 8Creating users
- 9Creating groups
- 10Policies for users and groups
- 11Assigning roles to groups
- 12Unassigning and offboarding
- 13Proving the model works
- 14What breaks
- 15Lab briefing: a role model for eight environments
- 16Lab solution walkthrough