Best practices for locking down navigation
Nov 25, 2015
Hi (again)! I'm wondering if there are some best practices out there to lock down your course navigation to make sure students complete a course. Being new to design, I'm not doing well with this.
We kept the menu open and navigable because we think some users will want to go backwards at times and review a section. But, if they use the menu to click through, then some users are not hitting all the subslides in a section and they're ending up showing an incomplete course.
Has anyone experienced this and have any recommendations?
Thanks so much!
6 Replies
In doing some reading, I see a note that Free, Restricted, and Locked Navigation is not working with HTML5, at least as of 09/15/15. Free navigation seems to work. Is it both restricted and locked that don't work?
Thanks again,
Hi Cheryl!
You can restrict or lock navigation in an Articulate Storyline course to prevent learners from skipping ahead without actually finishing the content. Here's how.
That's so strange. I took this screenshot last Wednesday (see attached Word document). The Player Menu section for Navigation was not checked. Then I found some recent discussions indicating this was an issue.
I'm glad it's working. That's so much easier than trying to figure workarounds!
Ah, looks like you have the Storyline 1 documentation.
Are you using Storyline 1 or 2?
Thanks, Leslie. That answers that! I have Storyline 2. I followed a link from a response 7 months ago. I guess that was too old. The documentation didn't say Storyline 1, just Storyline. I'm so new at this that I didn't consider a difference.
Thanks for clearing that up!
No worries Cheryl! Glad to be able to assist. Just let us know if you need anything further.
This discussion is closed. You can start a new discussion or contact Articulate Support.