Forum Discussion
Hardening Storyline 360 Courses Against Client-Side Completion/Score Manipulation
Hi Community,
We’ve identified a case where a learner manipulated client-side browser tools to force course completion and a passing score in a SCORM package built with Articulate Storyline 360.
I understand SCORM communication is inherently client-side, but I’m looking for best-practice mitigation strategies, such as:
- Gating LMS commit/score submission until final quiz pass
- Centralizing and controlling when completion/status is set
- Recommended LMS-side completion rules (e.g., result-slide–driven completion)
- Methods for detecting or flagging abnormal completion behavior
Any practical patterns or examples that significantly raise the barrier against this type of manipulation would be appreciated.
Thanks!
1 Reply
Hi Chittibabuko038!
I just wanted to pop in and highlight the Exchange Best Practices section of our community!
It's full of other Articulate users sharing insight and strategies on more out-of-the-box LMS configurations. That might be a great place to post this query as well!
I'll also open the floor here for other users to share their design suggestions with you!