A Solution for Securing Your Own Course Sharing and Acess Control for Client LMS Integration

Hi all,

When a corporate client wanted to track their staff's progress in our course using their own LMS, we needed a solution that protected our content and controlled access after the subscription expired. So I'd like to share our solution and if you encounte the silimar situation, hope it might be helpful. 

Situation:

1. We sell our own e-learning courses to customers(both B2B and B2C).
2. A corporate client purchases a course with unlimited users for a time period.
3. The course is made with Rise, including 15 lessons.
4. The client wants their staff to log in to their own LMS, not ours, so they can track progress from their end.
5. There is no need to track test results, but they want to know who and how many lessons users have taken.
6. We want to protect our product and ensure they cannot access our course after the expiration date.

Solution 1:
We can divide our course into lessons and add code to expire the lessons after the end date, then provide the packages for them to host the lessons in their own LMS. This approach involves the risk of trusting them not to break our code after the course is overdue.

Solution 2: (This is what we chose)

• We published our whole course (not individual lessons) without a menu and navigation and hosted it on our own server.
• We created a detecting page with SL. If the course isn't expired, it will open a new window, link externally to a lesson of our course, and close the original window. If it is overdue, it won't link to our lesson and will show an overdue message.
• We deliver 15 detect-page published files for the 15 lessons for the client to host in their LMS so they can track who and how many lessons their staff have taken.

This way, we ensured our content remained secure while meeting the client's tracking needs.

You are welcome to share ideas if you have different solutions that would also work for the situation.