Skip to main content
Question

Learning Plan Flexibility & Intelligence - Suppressing Irrelevant Notifications When Changes are Made

  • Nov 6, 2026 7:29 PM UTC
  • 2 replies
  • 10 views

1. What specific problem or challenge are you facing?*
The learning pan feature as a whole feels very static and not flexible or able to evolve the way our content does and how our organizational learning needs to. Right now, making changes to learning plans that are only supposed to apply to future enrollments tend to have negative impacts for existing users and retroactive implications. As an example, a user I’ll call Sally completed a learning plan in 2024. We added new courses to that learning plan over time (and ensured we checked off the “do not reset completion” for completed folks so they wouldn’t be impacted). Well, this user completed a course that had been added to the learning plan - not even through the learning plan, as a one-off for a new process. Because the learning plan had logic to unlock a course and trigger a notification about the unlocked content when the plan was complete, the user got that notification and was very confused. The user then spends time going in, checking to see what they need to do, and realizing everything is completed. The user then emails us, so we have to dig in and figure out why this happened and what’s going on. If learning plans were more flexible and intelligent, there would be a way for it to understand that a user who already unlocked and completed the content does not need this notification again.
 

2. What outcome are you expecting?*
The ideal state is a more intelligent learning plan process so people don’t get irrelevant notifications and so we don’t have to disable or re-word notifications to lessen their impact.
 

3. How will this feature impact your business and/or industry?*
It’s a better user experience to not get irrelevant notifications. It saves times for the user checking and the admin they reached out to verifying, digging in, and also saves time for docebo support helping figure out why a notification triggered when the entire plan was completed years ago.

2 replies

lrnlab
Hero III
Forum|alt.badge.img+10
  • Hero III
  • Nov 6, 2026 10:06 PM UTC

Hi ​@JennyG to log an Idea, please post it here so we can vote it up. Thank you.

https://community.docebo.com/p/idea-submission-template


Hi ​@JennyG, while we wait for a native platform fix, several proven community workarounds can completely suppress these retroactive notifications right now without waiting for new feature development. The core issue stems from the fact that adding new courses directly to an existing, completed Learning Plan disrupts the legacy tracking shell and triggers unintended automation triggers for historical users.

Here are the primary strategies currently used by other admins to break out of this loop:

1. The "New Version" LP Strategy (Highly Recommended)

Instead of updating an active learning plan that contains legacy completions, the safest approach is to treat learning plan updates like a new version rollout.

  • The Process: Duplicate the existing plan, add the new course to the new copy, and transition your automated enrollment rules or branches to target this new plan going forward.
  • Why it works: Historical users like "Sally" stay locked into their pristine 2024 completion shell. If they take the new course later as a standalone "one-off," it remains entirely separate and never crosses paths with their completed plan records.

2. Utilize Course Equivalencies

If you absolutely must add the course to the existing plan shell, you can use automated mapping to trick the tracking logic.

  • The Process: Set up a Course Equivalency Rule between an older course that the 2024 cohort already completed and the newly added course.
  • Why it works: When the new course joins the plan, the system evaluates the legacy users, detects the equivalency, and automatically marks the new item as Completed for them. This skips the "unlocked/in-progress" status change that causes the platform to push out the notification alert.

3. Restructure Notification Triggers via Dynamic Groups

Instead of letting the "New content in learning plan" notification fire broadly for everyone, restrict its operational scope.

  • The Process: Go to your notification settings and add a Trigger Filter. Change the target audience from "All Users" to a specific dynamic group or branch consisting only of active, ongoing cohorts (e.g., users enrolled after a specific cutoff date).
  • Why it works: Even if the learning plan triggers a backend content alert, the delivery engine drops the message for legacy users because they do not meet the active group filter requirements.