Guides
Page navigation locks and required answers
Restrict Previous, Next, page dots, and swipes without confusing locks with sequence defaults or required-answer rules.
Page locks restrict manual navigation while that page is active. They work alongside the Guide defaults, Sequence controls, player preferences, and required-answer rules.
You need Guide edit access to change them.
Set the locks
- Select the page.
- Open Page > Page settings > Runtime.
- Under Manual navigation locks, select the controls to lock.
- Select Save page.
- Preview the path, including its return and finishing behavior.
| Lock | Effect |
|---|---|
| Lock previous button | Removes ordinary Previous navigation and also prevents backward page swipes |
| Lock next button | Prevents manual forward page navigation when another page follows, including forward page swipes |
| Lock page dots | Removes page-dot navigation |
| Lock swipe navigation | Prevents page changes by horizontal swipes in either direction |
Sequence settings still decide which controls exist. Unlocking a control does not create one hidden by those settings. Changing a Sequence default does not remove a Page lock. A player's swipe preference can affect ordinary swipe availability, but it does not erase a Page lock.
The editor remains navigable for authoring. Test locks in Preview and Play, rather than expecting the authoring canvas to become locked.
Keep Finish and authored outcomes separate
Lock next button does not remove the final Finish guide action when the page has no next page. Hiding Next in Sequence settings also does not remove that final action. Required-answer checks can still block finishing.
Locks govern manual controls. They do not disable configured page-entry outcomes, timer outcomes, or answer-driven routes. If a page moves despite locked controls, check those authored actions.
A popup has its own Close popup control. Use it to return to the underlying page; locking page navigation is not a way to prevent dismissing a popup.
Understand required answers
In Play, unresolved required Fields can block forward navigation, routes to another sequence, and completion. Page-dot choices can also be unavailable when they would skip required work on intervening pages. Save the answer and wait for required media evidence to become ready.
Backward navigation within a sequence is treated differently from moving forward. Do not use a required Field as a substitute for a Previous lock.
Preview allows authors to inspect paths without the same required-answer departure guards. A successful Preview route alone does not prove a player can leave that page with unanswered required Fields.
Avoid a page with no way out
Keep at least one usable forward control or authored exit. A Show message, speech request, or splash does not move to the next page. A popup can return to the same underlying page.
Inspect Warnings and test each route, including with required Fields unanswered. Warnings can identify a navigation trap, but they are not proof that every player preference and answer state has been tested.
If someone is stuck, review the selected page's locks, Sequence settings, required Fields, and outcome destination. A timer that already attempted a blocked action does not automatically retry after the answer is fixed; supply a usable manual route or test a fresh visit.