Sequences and navigation

Sequences divide a Guide into ordered flows. Pages normally move forward in their authored order inside a sequence, while routes can send someone to a different page or the beginning of another sequence.

You need Guide authoring access and permission to edit its Library folder to change sequences or routes. People with play-only or read-only access follow the paths you publish but do not see the same authoring controls.

Organize sequences and pages

1. Open the Guide from Library and select Edit.
2. Open Sequence and select Add sequence. Give the new flow a name that distinguishes its purpose.
3. Open Organizer to review the entire Guide. Move sequences or their pages earlier or later, or select a sequence and use Add page.
4. Select the sequence where new full-Guide sessions should begin, then choose Sequence > Make start sequence.
5. Use Rename sequence, Duplicate sequence, or Delete sequence when needed, then review the Guide's paths again.

The Start sequence opens on its first page. Sequence order helps authors organize the Guide, but reaching the last page of one sequence does not automatically open the next sequence in the Organizer. Add an explicit route when a path should continue into another sequence.

Choose the player controls

Open Sequence > Sequence settings, then review Player navigation:

• Show previous button lets players return to the prior page or return from a routed path when that return is available.
• Show next button lets players advance in the current sequence when no authored route takes over.
• Show page dots displays the pages in the current sequence and lets the player move to an available page.

These settings control visible player navigation; they do not create routes between sequences. A required Field can still prevent forward navigation until a valid answer is saved. Hiding every forward control without an automatic or routed way out can trap the player and produces a severe warning.

Route to another page or sequence

Use a page-entry route when the move should happen automatically as a page opens:

1. Select the source page and open Page > Page settings.
2. Open Entry and set Page-entry action to Route page or Route sequence.
3. Choose the destination. A sequence route always opens that sequence's first page.
4. Save the page and test the path in Preview.

A Field answer method can also use After submit to open the next page, a selected page, or a selected sequence start. A single-select Tap choice can use a different destination for each final choice; a choice group with sub-choices does not route. See Field blocks and Tap choice answers for those controls.

Routes keep pointing to their selected destination when you reorder or rename content. Deleting that destination makes the route unavailable, so open Warnings and Preview every path after structural changes.

Fix common problems

• If full Preview or Play starts in the wrong place, select the intended sequence and choose Make start sequence.
• If another sequence is unreachable, add a page-entry or Field route to its start instead of relying on sequence order.
• If a route skips content immediately, review the source page's Page-entry action; use None when the page should remain visible.
• If the player cannot move forward, answer required Fields and confirm that a next button, page dot, automatic action, or usable route remains available.
• If a destination is missing, choose an existing page or sequence, save the source settings, and Preview the path again.