For Entra ID, the user can be deleted in Laserfiche Cloud after they are permanently deleted from the user directory in Entra ID. Currently we only support these two idPs.

We are actually evaluating this feature, although it’s not on our current roadmap. If you’re able to share more about your use case, it would help us review and possibly reprioritize it.


 

We’re currently evaluating whether a move to Laserfiche Cloud is feasible for our organization, and one major concern is how SCIM provisioning works with Okta. Because we rely on Okta and have a high volume of users cycling in and out, the inability to fully delete SCIM‑managed accounts would leave us with thousands of Inactive users in Laserfiche. That would create unnecessary clutter and complicates our access audits, since inactive accounts would still technically exist and could be viewed as a security risk.

I don't believe this is unique to us. Many of the education institutions I work with would face the same issue—only at a much larger scale. Student accounts turn over every semester or year, and without true deprovisioning, they’d accumulate an enormous number of stale accounts if they used SCIM with Okta.

Another reason I think it would be important to have this feature is the inconsistency between identity providers. Since Laserfiche supports full SCIM deprovisioning for Entra ID, but not for Okta, that discrepancy makes it difficult to set clear expectations and creates an uneven experience across environments. Ideally, SCIM behavior should be standardized across all supported IdPs so organizations can plan their identity lifecycle management with confidence.