JML Automation
One leaver. Three connected findings.
When an employee is deactivated in Okta, Mima automatically identifies every active licence seat, unapproved AI session, and SaaS subscription tied to that identity. Reclamation workflows stage for approval or execute via approved workflows depending on your policy. The ghost seat, the active AI session, and the resulting GDPR exposure are resolved in a single connected finding — not three separate tickets across three separate tools.
Every JML action is logged with a Merkle-signed record. If an auditor asks why a Named User licence was reclaimed on a specific date, the answer is a cryptographically verifiable log entry. Not a spreadsheet. Not a memory.
Employee offboarding event received agentlessly via HR integration.