A client wants to protect access to their courses. Possibly a time-based lockout added to the the wrapper before zipping the course? Something along those lines.
I am struggling to think of an effective way of doing this that couldn't be easily removed/circumvented. Any thoughts or pointers on this?
Hi Matt, Yes, the client will be using their own in-house LMS. I had considered the JS route and then possibly modify the terms of use in the contract.
Could possibly put something in to the HTML files before zip up and deployment too but that would be less secure?
4 Replies
Within the Storyline course itself?
LIke if a user leaves it open for 15mins it auto shuts down and closes the course?
Hi Matt,
Yes, the client will be using their own in-house LMS. I had considered the JS route and then possibly modify the terms of use in the contract.
Could possibly put something in to the HTML files before zip up and deployment too but that would be less secure?
To help anyone out who is having the same issue, I found the following post:
https://community.articulate.com/discussions/articulate-storyline/setting-an-expiry-date-for-published-content
Done a quick proof of concept and it seems to work OK. A bit more finesse and this should be close enough for me!
Glad you were able to find something that would work for you Simon. Thanks for popping back in to share with the community.
This discussion is closed. You can start a new discussion or contact Articulate Support.