How to lock down navigation in Lectora

If you want to guide users through your courses, and ensure that they are learning all that they need to, locking down page navigation is a great way to start.

This means to disable navigation buttons such as next or back to ensure a user completes activities before allowing them to continue. This stops your user being able to rapidly click through your course to say that they’ve finished the module.

Navigation lockdown is achieved in two stages…

  1. Deactivation
  2. Reactivation


To deactivate our “Next Page” button, click on the page and add an action with the following properties…

  • Trigger : On page show
  • Action : Set State
  • Target : Next Button
  • State : Disabled


Next, we must tell Lectora when to re-enable the Next button. If your question or activity has a submit button, we can use that to reactivate our navigation. Add an action to the submit button with the following properties

  • Trigger : On Mouse Click
  • Action : Set State
  • Target : Next Button
  • State : Enabled

Conditions (Optional)

If you like, you can choose to have your next button activate only if the answer was correct.

To this, we use conditions. Conditions gives you further control on how and when actions occour. To create a condition, click on the conditions button in the actions tab where we just were. With the conditions creator, we are going to choose the variables that will form the basis of our conditions. Under variable, we are going to choose “Question 2”, and the relationship will be ‘is correct’. This means the Next button will activate only if the question was correct, and the user will be allowed to continue to the next page.

Initially Disabled (Lectora 17)

In Lectora 17, there is an option to ‘initially disable’ a button when the page loads. This means that a button will be disabled from the moment the page loads, without having to create an action.

To do this…

  • Click on the button
  • Click on the properties tab
  • Check the box that says “Initially Disabled”.

Remember though, If you navigation button is inherited into multiple pages, it will be initially disabled on every page it appears on. If you don’t want this, using actions is the preferred method.

Thanks for watching. If you have any questions at all, feel free to visit us at, or contact our support line at

Leave a Reply