> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ally.security/llms.txt
> Use this file to discover all available pages before exploring further.

# Building a Custom Quest

> Walkthrough of the Custom Quest workflow in Ally Security, covering scenario design, exercise preparation, and running tabletop exercises end to end.

**Build** (Quests in the app) is where you create drafts, fill profiles, generate scenarios, and pick one to refine. **Run** is where you prepare published quests, start dry or live exercises, and review finished work. Each area uses a board with columns that group quests by stage so you can see what needs attention.

**Custom Quest** itself is a guided path: naming and kind, organization and quest profiles, scenario selection, optional inject design, then the **Quest Lobby** for readiness, sharing, and entering exercises.

## How the Wizard Works

The **sidebar** tracks steps in order; you can move between steps once validation passes. **Autosave** runs when you use Next, Back, or the sidebar, provided your quest has a valid, unique **name** so the draft can persist. **Save and exit** saves and leaves the editor—from the **Quest Lobby** or **Inject Designer** you land on **Run**; from earlier steps you land on **Build**. **Discard** removes the draft after confirmation and returns you to **Build**.

## Scenario Generation

Opening **Select Scenario** saves your quest, then generation runs from your profiles. If it fails, fix issues and use **Try again**. Existing results are not regenerated automatically unless you retry from the error state.

## Where to Go Next

The pages in this section follow the builder sidebar order.
