Skip to main content
Question

Archiving Learning Plan Enrollments - Inactive Employees

  • March 2, 2026
  • 9 replies
  • 21 views

kfontanini
Helper I
Forum|alt.badge.img

My coworker and I are trying to archive/unenroll our 2025 Learning Plans, and while we were excited about the new Archive feature, we did notice a limitation. It looks like we can only bulk archive/unenroll active employees. Has anyone else run into this?

For anyone working for Docebo, are there plans to change this? With the current setup, we will still have to go through course-by-course to archive the inactive users. I know some people will keep inactive users enrolled in courses since you can exclude them from reporting, but we usually clean things up so we can get a clearer picture of how things are being utilized. 

9 replies

Forum|alt.badge.img+4
  • Helper III
  • March 2, 2026

I can unenroll deactivated employee.  Are you trying to use Select All, because that doesn’t work with Active or inactive.  But you should be able to do inactive in groups of 100.


lrnlab
Hero III
Forum|alt.badge.img+10
  • Hero III
  • March 2, 2026

Interesting I was not aware of this limitation. Did you reach out to support to ask if this is intended or perhaps a bug?


Forum|alt.badge.img+4
  • Helper III
  • March 2, 2026

@lrnlab My understanding is it’s intended and used as a system load limiter. I found it odd since it runs as a background job anyway, so maybe someday they’ll remove that.


kfontanini
Helper I
Forum|alt.badge.img
  • Author
  • Helper I
  • March 2, 2026

I can unenroll deactivated employee.  Are you trying to use Select All, because that doesn’t work with Active or inactive.  But you should be able to do inactive in groups of 100.

I’m aware of the limitation on using Select All. When I tested archiving/unenrolling one person from the Learning Plan, an error message popped up saying I couldn’t do it because the person was inactive. Otherwise, the archive/unenroll has been working for me.


kfontanini
Helper I
Forum|alt.badge.img
  • Author
  • Helper I
  • March 2, 2026

Interesting I was not aware of this limitation. Did you reach out to support to ask if this is intended or perhaps a bug?

My coworker has a ticket open with support, and we’ll share what we’re seeing with them. I’ll update my post when I learn more.


kfontanini
Helper I
Forum|alt.badge.img
  • Author
  • Helper I
  • March 2, 2026

Interesting I was not aware of this limitation. Did you reach out to support to ask if this is intended or perhaps a bug?

My coworker has a ticket open with support, and we’ll share what we’re seeing with them. I’ll update my post when I learn more.

 


kfontanini
Helper I
Forum|alt.badge.img
  • Author
  • Helper I
  • March 2, 2026

@lrnlab My understanding is it’s intended and used as a system load limiter. I found it odd since it runs as a background job anyway, so maybe someday they’ll remove that.

Did you see that documented somewhere? I’ve been trying to read through the documentation, but I may have lazy looked and skimmed right past it.


Forum|alt.badge.img+4
  • Helper III
  • March 2, 2026

@lrnlab My understanding is it’s intended and used as a system load limiter. I found it odd since it runs as a background job anyway, so maybe someday they’ll remove that.

Did you see that documented somewhere? I’ve been trying to read through the documentation, but I may have lazy looked and skimmed right past it.

No, I think was just in conversation with support when it first rolled out.  


lrnlab
Hero III
Forum|alt.badge.img+10
  • Hero III
  • March 2, 2026

@mzirnhelt that makes sense since they gave us the same “warning” for course archiving where they recommend no more than 200 at a time