Question

Best Practices for Content Access and Enrollment Management in LMS: Seeking Insights and Features

  • 17 April 2024
  • 6 replies
  • 37 views
A
Rank

Hi everyone!

I'm seeking insights on best practices for content access management in our LMS. Specifically, we have a course hierarchy where 'Level 2' should only be accessible to users who have completed 'Level 1.' Currently, our approach involves creating a 'Level 2' group with enrollment rules to automatically add users who have completed the 'Level 1' course. This group is then assigned a catalog featuring the 'Level 2' course, ensuring visibility only to eligible users. Is this method considered effective, or are there better alternatives?

Additionally, we've been asked if users who haven't completed 'Level 1' can request placement on a waiting list or similar. Is there a feature within Docebo to manage such requests?

6 replies

jlreonal
Rank
Userlevel 5
Badge +2

Hello - Your approach to create an automatic group to capture learners who completed L1 and assign with L2 catalog is the best viable solution. I would do the same thing for the same requirement… As for your question 2, if I understood it correctly, you want learners who have not completed the L1 can request L2 but on waitlist?

A
Rank

Hi,

Thank you for confirming our approach. Regarding the second question, yes, we're looking into allowing learners who haven't completed 'L1' to request access to 'L2' but be waitlisted until prerequisites are met. Is there a feature or workaround in Docebo (or elsewhere) for this?

Appreciate your insights.

jlreonal
Rank
Userlevel 5
Badge +2

Hi,

Thank you for confirming our approach. Regarding the second question, yes, we're looking into allowing learners who haven't completed 'L1' to request access to 'L2' but be waitlisted until prerequisites are met. Is there a feature or workaround in Docebo (or elsewhere) for this?

Appreciate your insights.

You can achieve this using a learning plan… add the two courses to your learning plan and make L1 course as prerequisite to your L2 course. Note that learners will need to be enrolled in a learning plan to meet this requirement. Learners will see both courses once enrolled in the learning plan, but they can only access L2 upon completion of L1 course.

dwilburn
Rank
Userlevel 5
Badge

I agree with @jlreonal as you are jumping through a lot of hoops for Catalog visibility. We drive the majority of our learning through Learning Plans. If you substitute Learning Plans for Catalogs then this gets much easier.

We have a few power user profiles that drive the Learning Plan enrollments.

A
Rank

Thank you both for your insights!

Regarding the use of learning plans versus catalog visibility, I'm seeking more information on the pros and cons of each approach. What factors make one method intrinsically better than the other? Additionally, we offer a training program that has been available for over a decade, so some clients may have completed the course before our LMS was implemented. In such cases, we're considering implementing a form within the LMS where clients can request access to the course. We would then manually verify their completion status using our CRM. Any thoughts on how to effectively manage access in this scenario would be greatly appreciated.

dwilburn
Rank
Userlevel 5
Badge

@AFaraj - Catalogs and Learning Plans are not mutually exclusive. We train internal employees and external vendors.

In both cases we assign most of the training to the users through Learning Plans that are in Catalogs. The user then works through the e-Learnings in the Learning Plans and typically finishes up with an ILT. But there are e-Learning only Learning Plans.

We also have training that is done at the course level through group enrollments. These are periodically assigned on a specific cadence. They are not on a Learning Plan.

Our internal employees have access to the content in the Catalogs allowing them to enroll in Learning Plans and or courses. But they do not typically do that.

We primarily use Catalogs to control visibility. Users in the internal branch can see all of the catalogs. Users in the external branch can only see specific catalogs.

Reply


Terms & ConditionsCookie settings