Sequences and navigation

Sequences divide a Guide into ordered flows. New full-Guide sessions start at the first page of the Start sequence. Reaching a sequence's last page does not automatically open the next sequence in Organizer.

You need Guide authoring access and permission to edit its Library folder.

Organize the flow

Use Sequence > Add sequence, Add page, and Organizer to build and order the Guide. Rename, duplicate, and delete controls are described in Guide structure.

Select the intended starting sequence and choose Sequence > Make start sequence. You can also use Make start under Guide start in Sequence settings. This saves immediately; it does not wait for Save sequence, and Cancel does not undo it.

Changing the Start sequence affects new full-Guide launches. A page-targeted Preview still starts at its target.

Edit Sequence settings

1. Select the sequence, then choose Sequence > Sequence settings.
2. In Sequence, change its Name or Player navigation controls.
3. In Pages, use the reorder handles to change the page order.
4. Select Save sequence.
5. Preview the changed path and check its first and last pages.

A blank name or Changed elsewhere conflict can disable saving. If a save fails, check both the page order and settings before retrying: reordering and saving the other settings can finish separately.

The Cloud voice section changes the sequence's voice binding immediately through its selector. It does not wait for Save sequence. See Guide speech.

Choose player controls

Control	Purpose
Show previous button	Returns to an earlier page or an available routed-path return
Show next button	Advances to the next page in this sequence
Show page dots	Offers page-position navigation within the sequence
Enable swipe navigation	Allows horizontal page-navigation gestures

Untouched controls use Guide defaults in the settings dialog. Changing a control creates an explicit choice for that sequence.

During playback, explicit Sequence Previous/Next choices take priority over personal preferences, then Guide defaults. Page dots use Sequence then Guide. Personal swipe preference takes priority over the Sequence swipe choice. Page locks and required answers can further restrict available navigation.

Hiding Next does not remove the final Finish guide action when no next page exists. These switches do not create routes between sequences.

Connect sequences and pages

Use Page settings > Entry > When this page opens for an automatic entry outcome. Go to page selects a page; Go to sequence start opens another sequence's first page. Configure the destination and timing, save, and Preview. See page-entry outcomes.

Page timers, supported Block tap actions, and saved Field-answer outcomes can also choose a path. Their timing and triggers are separate. Consult the relevant Block or answer-method instructions when designing answer-driven navigation.

Renaming or reordering a destination keeps its identity. Deleting or moving it can leave an old route unavailable. Re-select the destination, save, and review Warnings after structural changes.

Check a blocked path

Confirm the launch target, available controls, Page locks, required answers, and route destination. A message or splash alone does not provide a way to the next page. Test returning from routed paths as well as going forward.

Preview does not enforce the same required-answer departure guards as Play. Use the actual player workflow when checking those restrictions.