Guide overview

Guides present instructions, media, and questions as an interactive experience. An author builds the experience in Library; a player follows its pages and answers any Fields included in the path.

Understand the parts

A Guide is the complete item stored in a Library folder. It contains Sequences, and each sequence contains ordered Pages. Pages hold Blocks: Text for written content, Media for an image, video, or audio item, Field for a prompt with answer methods, and Flashcard for question-and-answer content that players can flip.

One sequence is the Start sequence. A simple Guide can use one sequence with several pages. More complex Guides can use routes between pages and sequences. Selecting something to edit does not make it the starting point for players. See Guide structure.

Start an authoring task

1. Open Library and enter the destination folder.
2. Select Create > New Guide. Enter a name and optional description, or enable Use template and select a Guide template.
3. Select Create guide to open the new Guide in its editor.
4. Add pages and blocks. Use the Guide, Sequence, and Page menus for settings and structural actions.
5. Open Warnings, then use Preview to test the experience. Preview does not create a Reports inbox record.
6. Return to Library and use Play when you want a normal run.

To continue an existing Guide, select Edit from its available Library actions. The creation walkthrough explains the first page, blocks, and saving. The editor controls guide shows where the same tools appear on phones and larger screens.

Know which access you need

Authoring requires edit access to the containing folder and a workspace that allows creating and editing content. A folder Owner or Editor can have the needed folder permission; a Viewer cannot edit simply because they can open the Guide. An archived Guide is read-only until it is restored.

Creation can also fail when the destination workspace cannot accept more authored content. Check its Usage and access state if the action is unavailable. See workspace allowances and Library deletion and restoration.

Save and test deliberately

Structural actions save as they complete. Settings and Block Editor dialogs have their own save actions. There is no separate whole-Guide Publish step; the saved Guide is the current authored version. Keep the editor open if a save fails, and resolve the message before leaving or testing that change. See Guide saving for dialog saves, autosave, and retries.

Use Preview after changing content, ordering, or routes. A normal Play session records progress and saved answers; natural completion triggers Report capture after unresolved session changes finish syncing. See Preview and Play and completion Reports for those workflows.

If a Guide seems missing, check the Library source and folder, including its archive view. If Edit is missing, check folder permission and workspace availability. Access to a shared Guide lasts only while the applicable access to its containing folder remains available.