Joiner-Mover-Leaver (JML) Governance

Users' access needs change when they join, move or leave the organization. Joiner-Mover-Leaver processes help the organization keep identities, responsibilities and entitlements updated throughout the user lifecycle.

Use case

Employees' access needs change over time. When a person joins, changes role, changes manager, receives new tasks or leaves the organization, identities and entitlements need to be updated in a controlled way.

Without clear lifecycle governance, organizations risk that entitlements become incorrect, remain in place too long or no longer reflect the user's current role and responsibility.

Organizations therefore need to manage identity changes as a controlled process. This can include ensuring that:

• new users get the right identities and entitlements from the start
• role and organizational changes lead to updated access
• manager, responsible person and organizational affiliation remain correct
• entitlements are removed when they are no longer needed
• terminated users do not retain access to systems and resources

The result is better control, reduced risk of incorrect entitlements and clearer traceability throughout the user lifecycle.

How Fortified ID supports this

Fortified ID Control can be used to automate and govern lifecycle events between HR systems, directories, applications and other business systems. Pipes and Valves can process, synchronize and update identity and entitlement data when a user joins, changes or leaves.

Forms can be used for controlled processes during onboarding, changes and termination. Approval Flows can ensure that the right responsible people review and approve changes when needed, while Schedules can initiate recurring checks of users, entitlements and responsibility relationships.

Reporting and Auditing can provide evidence for following up lifecycle events, decisions and completed changes.

Fortified ID Access can complement the process by protecting access to systems and resources throughout the user lifecycle. Strong authentication and step-up authentication can be used when higher security levels are required for particularly sensitive actions.

Examples

• Automated onboarding of new employees from an HR system
• Updating identities and entitlements during role or organizational changes
• Change of manager or responsible person
• Automatic removal of access when employment ends
• Synchronization of identities and entitlements between HR systems, directory services and business systems
• Review and follow-up of identities throughout the user lifecycle