Skip to content

Handle joiner, mover and leaver events

JML work happens on Identity & Access → Lifecycle → Joiners, movers, leavers (page Identity Lifecycle (JML)). Starting, approving and pausing events needs Identity Admin, Tenant Owner or Super Admin. A Manager can approve or reject joiners assigned to them.

How events arrive

Events started from AtmanID itself, and a termination date that arrives, run the complete workflows described below. The other sources are narrower:

Source What it actually does
Joiner, Mover, Leaver buttons on the JML page; Offboard Now on the Contract ending tab The full workflows below
Identity sources (HR feeds such as Workday or Rippling), on their schedule or Run Sync Now Adds new people as active, updates changed fields, sets leavers to inactive and opens revocation tickets. It does not grant birthright access, provision accounts or run the leaver steps.
HRIS API (POST /api/v1/jml/joiner, /mover, /leaver, API-key scope write:jml) Joiner: creates or reactivates the person (as pre-hire if the start date is in the future). Mover: updates department and title. Leaver: sets the termination date. No accounts are provisioned or revoked by the call itself. Each call records a Pending event. The leaver event completes on the termination date, when the leaver runs. Joiner and mover events stay pending until you run the Joiner or Mover workflow for that person, which completes them.
Termination date reached, or the end of gardening leave or a notice period (daily, 12:00 UTC) The full leaver workflow below, run by the system. It keeps the termination date HR set.

A termination date set through the HRIS API or by hand is enough for the full leaver to run on that date. An HR feed that only marks a person inactive is not: start those departures from the Leaver button.

If the scheduled run cannot finish a leaver, it still sets the person to deprovisioned so they cannot sign in, and the run is reported as failed under Platform Config → Operations → Scheduler with the reason. Finish the clean-up with Offboard Now. A scheduled leaver that would remove your last Tenant Owner is refused and reported the same way.

Joiner

Click Joiner, choose the Identity (it must already exist), and optionally a Department, Title and Hire Date. Then:

  1. Auto Birthright Access works out the starting access from your Birthright Access Profiles and preselects those applications.
  2. With Require Manager Approval, the button reads Submit for Approval. Birthright entitlements are granted straight away, but applications are provisioned only after the manager clicks Approve & Provision. Reject removes the birthright entitlements again.
  3. Each application gets an account through its connector if the connector can create accounts. Otherwise a ticket is opened, and sent to Jira or ServiceNow if you have connected one.
  4. The new starter receives a welcome email.

The joiner does not schedule an access review, 30-day or otherwise. Someone returning after deprovisioning is detected as a re-joiner. Their HR sync is paused for 30 days, and earlier login IDs can be reused.

Mover

Click Mover and enter New Department, New Title or New Role. The mover updates the person and opens a review ticket for each application you chose to review, and a pending account for each new application. It does not grant the new department’s birthright access by itself. It then compares old and new birthright access: leftover low-risk access is revoked automatically, and anything else becomes a revocation ticket. A certification campaign is started only if you have a MOVER certification trigger rule.

Leaver

Click Leaver and choose the Identity, Termination Date and Reason. The Blast radius panel shows how many AI agents the person owns. Tick the confirmation and click Trigger Leaver. The workflow:

  1. Disables each app account through its connector, or opens an urgent revocation ticket where there is no connector. For a person on leave, this includes the accounts that Pause disabled in AtmanID only.
  2. Sets the person to deprovisioned and cancels their unused email approve/reject links.
  3. Suspends their live sessions. This applies only when session enforcement is on; in shadow mode it is only recorded.
  4. Flags the machine identities they own as orphaned, and deactivates the AI agents they own. Agents with a managing team keep running and are flagged for a new owner instead.
  5. For each Exchange Online application: removes inbox forwarding rules and removes the person from Microsoft 365 and security groups. Classic distribution lists are left for manual removal, and a PowerShell command is returned for each.

An out-of-office reply, calendar delegation and keeping the mailbox as shared are API-only (not on the Leaver form). Shared-mailbox conversion is always handed back as a manual PowerShell step: Microsoft Graph cannot do it.

The leaver does not remove the person’s entitlement records in AtmanID; it acts on their app accounts. A leaver is refused if it would remove your last Tenant Owner.

JML policies

Under Policy Engine, New Policy creates a rule. A rule matches by Event Type, Department, Identity Type and Title Contains, and lists applications to Provision, Review or Deprovision. Policies only preselect applications in the Joiner and Mover forms. They do not run on their own. Dry-run only keeps a rule out of live matching.

Pause and return

Pause places an active person on leave. Choose a Leave type: Leave of absence, Sabbatical, Secondment, Notice period, Gardening leave or Suspension. Their app accounts are disabled or revoked in AtmanID (no connector calls), and the AI agents they own are suspended, except during a secondment. Return re-enables the accounts and restores only the agents that the pause suspended. Leave of absence, sabbatical and secondment return automatically on their end date. Gardening leave and notice period end as a leaver. A suspension can only be ended by hand.

Watch progress

The Activity view lists events by All Events, Joiners, Movers and Leavers. Each event has a status of Pending, Pending Approval, In Progress, Completed, Partial or Failed. Open an event for its Application Breakdown. For a partial or failed event, use Retry (New Event) or Mark Remedied. Events stuck in progress for more than two hours are closed as partial or failed automatically. Timeline shows one person’s history; pauses do not appear in it.

Audit events: JML_JOINER_TRIGGERED, JML_JOINER_PENDING_APPROVAL, JML_JOINER_APPROVED, JML_MOVER_TRIGGERED, JML_LEAVER_TRIGGERED, AGENT_DEACTIVATED_ON_LEAVER, FORWARDING_RULES_REMOVED, DISTRIBUTION_GROUPS_REMOVED, JML_PAUSE_TRIGGERED and JML_RESUME_TRIGGERED.

© AtmanID · Privacy