Joiner Mover Leaver (JML)
Automate user lifecycle management in Cakewalk. Learn how Joiner–Mover–Leaver (JML) workflows handle onboarding, role changes and offboarding to keep access aligned and least-privilege enforced.
👥 Who It Applies To
Admins
Configure and monitor JML workflows across the organization.
Managers
Trigger onboarding and offboarding for their own reports.
📖 Key Concepts
Joiner: A new employee or contractor starting at your company. Onboarding ensures they receive the right apps and permissions from day one.
Mover: An existing employee changing role, team, or department. Movers trigger adjustments to apps and permission levels in line with their new responsibilities.
Leaver: An employee or contractor exiting the company. Offboarding removes their access, ensuring no orphaned or stale accounts remain.
💡 Why this matters: JML workflows automate lifecycle management, enforce least privilege, reduce IT workload and close security gaps during role changes.
🛠 JML Workflows
Joiner (Onboarding)
Definition: Bringing a new user into the organization with the right baseline apps and permissions.
Navigation: User Overview → +New (manual) or auto-sync from HRIS/IdP.
How it works:
Synced users (default): Cakewalk creates a Review onboarding task, which must be confirmed before onboarding starts.
Synced users (No-Touch Onboarding): You pick up to 100 synced IdP groups for your Users integration. A new user in any of those groups is onboarded automatically, with no review task, when their manager in your company's HRIS or IdP matches a user in Cakewalk. Your IdP or Agent Cake creates the accounts in apps with automated provisioning. Every other default app gets an action task for the assignee the app's policy names.
Manual onboarding: Onboarding begins immediately once the Admin or Manager creates the user.
After confirmation (for synced default), the automatic start (for No-Touch Onboarding) or creation (for manual), apps and permissions are assigned based on group membership and selected apps.
Outcome: User becomes Active in Cakewalk with all required apps and access.
Why this matters: Synced joiners are validated before activation by default. No-Touch Onboarding removes this step for high-volume teams. Manual joiners allow immediate onboarding when speed is required.
💡 To turn on No-Touch Onboarding, go to Settings → Data sources → Users → Manage integration settings, turn on Sync managers and pick the groups. The groups come from your group sync, so connect that first under Settings → Data sources → User groups.
Mover (Role/Team Change)
Definition: Updating access automatically when users change roles, teams, or departments.
Navigation: User Overview → Edit User or triggered via HRIS/IdP sync.
How it works:
Group membership is updated (via sync or editing the group in Cakewalk).
Grant Access requests for default apps in the new group are created automatically.
Remove Access requests for apps no longer needed are also auto-created.
Requests from a group change skip every review step, so no approver is involved. They go straight to the action step of the app's policy: your IdP or Agent Cake makes the change where provisioning is automated, and every other app gets an action task for the assignee that step names.
Outcome: Access footprint aligns with the user’s current responsibilities.
Why this matters: Prevents over-permissioning and ensures least privilege as roles evolve.
Leaver (Offboarding)
Definition: Revoking access and cleaning up accounts when a user leaves the company.
Navigation: User Overview → contextual menu → Offboard user (manual) or auto-sync from HRIS/IdP.
How it works:
Synced users (HRIS/IdP): Cakewalk creates a Review offboarding task, which must be confirmed before removals begin.
On-demand offboarding: Admins or Managers initiate the user's offboarding directly in Cakewalk, which immediately generates removal requests.
Once confirmed (for synced) or triggered (for manual), Cakewalk generates removal requests for all managed apps the user has access to.
Before the offboarding starts, you designate successors: a new manager for each direct report and a new owner for each owned app, chosen from the app's other users. When the leaver is an app's only user, you can archive the app instead. A leaver who owns your company's HRIS or IdP connection needs a new connection owner, and each required person property on an app that is set to the leaver needs a new person.
When all tasks are complete, user status changes to Deactivated.
Outcome: All access is removed consistently and the history is logged for audits.
Why this matters: Ensures all access is removed on time, closing gaps that could leave orphaned accounts or active sessions exploitable after someone leaves.
Setting Up Assignees for On/Offboarding Tasks
Navigation: Settings → Data sources → Users → Manage integration settings.
How it works:
Define which tasks should be created for each event (Joiner, Mover, Leaver).
Assign default assignees for each task (e.g., Admin(s), Manager).
Save configuration.
When onboarding/offboarding is triggered: Tasks (e.g., Review onboarding/offboarding) are created and routed for confirmation.
Why this matters: Ensures steps are consistently handled by the right assignee according to your company guidelines.
Monitoring & Reporting
Status Transitions: JML workflows are reflected in the user’s status (Discovered → Invited → Active → Offboarding → Deactivated). Discovered accounts an admin chooses not to manage move to Ignored.
Offboarding Status: A leaver stays Offboarding while any removal is open and turns Deactivated only once all are done. Before that, Cakewalk checks for managed app access still on record and creates a removal for each one it finds.
On/offboarding overview: Review all pending and upcoming offboarding to review progress and follow up with assignees of outstanding tasks for timely completion.
Audit Export: Under Users → On/Offboardings, select Export to download the list as CSV or JSON. It includes completed onboardings and offboardings, each with its Completed at date.
Why this matters: Auditable JML flows support ISO 27001, SOC 2 and other compliance frameworks.
📋 JML Actions at a Glance
Onboard (Joiner)
Admins, Managers
User added on demand (immediate), via HRIS/IdP sync (review task first) or via No-Touch Onboarding (no review task) → default apps provisioned
Fast, compliant onboarding with governance checkpoints
Update access (Mover)
Admins
Group/role changes update access automatically
Enforces least privilege, avoids over-permissioning
Offboard (Leaver)
Admins, Managers
Offboarding triggers removals immediately; synced offboarding creates a review task first
Prevents stale/orphaned accounts while keeping governance controls
Configure JML tasks
Admins
Define default assignees for Joiner and Leaver events
Ensures consistency and accountability
Monitor JML status
Admins
On/Offboardings lists progress and completion dates and exports to CSV or JSON
Provides audit trail for compliance
🤖 With Agent Access
When your company also runs Agent Access, the lifecycle covers Agents too. A leaver's Agent Access is removed with everything else and the Connections their Agents used are revoked; a mover's Agents follow the new department, team and location at their next action. See User Lifecycle.
Last updated
Was this helpful?