Forum Discussion
Date limit or password protect course
Hello,
I'm looking into ways of protecting our courses from being illegally redistributed or accessed after a certain date. The two ways I have thought of so far are either to use the built-in JavaScript functionality to get a password from a server and having the user enter the same password to proceed beyond the first slide, or to disable any access beyond the first slide after a set date.
Is something like this feasible either through current features, or JavaScript inside Storyline 2? I'd love to hear your thoughts!
Just tested Matthew Bibby's solution in 360. In order to make it work, I needed to delete the T/F variable and replace it with a Text variable of the same name. It's attached.
Its perfect. Worked like a charm. Thanks.
I'm sorry to say that this is not a good solution if your goal is to provide the SCORM to the customer and make the course expire after a given time. The problem is that the JavaScript code you write in the Storyline project is perfectly readable and editable by the customers and thus they can change the expiration date whenever they want and extend the lifetime of the course. In other words, this solution is not reliable for you as a content provider.
The only reliable solution would be a core feature in Storyline but it seems they don't care about this because after 6 years (!) they haven't still provided it.
Any update on this topic?? any possible update on this in near future?? it's an important function that has been asked 8 years ago.
ditto
The solution is to use a 3rd-party provider which specializes in managing the distribution of your published learning content.
SCORM Cloud is a SaaS application that lets you manage all of your eLearning in one hosted platform. If you want to deliver your courses to learners via third-party LMS' but still maintain ownership and control of those courses, then SCORM Cloud Dispatch can help.
Dear Articulate Storyline,
Not everyone distributes e-learning on their own LMS. We provide off the shelf content that our customers want to host themselves. I don't imagine this is a terribly rare occurrence.
Can you please look into adding the expiry date functionality so that our content is secure even when distributed as a zip file.
Thanks.
I'm very disappointed that this issue hasn't been resolved over such a long period. Hopefully someone sees this and is able to incorporate the necessary changes.
