[ SYSTEM_DIRECTORY / JML_AUTOMATION ]

JML Automation

One leaver. Three violations prevented.

+ + + +

When an employee is deactivated in Okta or Active Directory, Mima automatically identifies every active licence seat, AI tool OAuth grant, 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 ChatGPT session, and the resulting GDPR exposure are resolved in a single 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.

[ THE JML DEPROVISIONING FLOW ]
1. TRIGGER: Okta / Entra ID Deactivation[ WAITING FOR DISCOVERY ]

Employee offboarding event received agentlessly via HR integration.

2. DISCOVERED VIOLATIONS (Single Scan)
Scanning active tokens and entitlements...
3. CRYPTOGRAPHIC RECORD
Compiling telemetry ledger...
4. SIMULTANEOUS PERSONA ROUTING
Pending webhook triggers...