# See Your Mission in Context: Launch Flow Moves to the Side Panel

<figure><img src="/files/Ga6u77QLWcOYbeF8v5sZ" alt=""><figcaption></figcaption></figure>

Launching a mission used to mean losing sight of everything else. The dialog modal opened in the middle of the screen with a small embedded mini-map that showed only the mission's waypoints, no zones, no other active drones, no annotations, no dock location. Operators reviewing a mission against the wider operational picture had to launch from memory or close the dialog, check the map, and start again.

The new Panel launch flow moves the mission and Go To Location launches from the center modal to a right side panel, keeping the main map fully visible throughout. When you select a mission, the main map re-centers and zooms to the mission area, so the waypoints appear in context with the zones, annotations, dock, and other active drones already on your map.

### What Changed

The launch workflow now has two options:

* Dialog — the existing center-screen modal flow. Mini-map embedded inside the modal.

<figure><img src="/files/s8SGGhFBgqs4IZZLAZO6" alt=""><figcaption></figcaption></figure>

* Panel — the new right side panel flow. Main map stays visible and re-centers on the mission.

<figure><img src="/files/qelVEQm2ALuUrJBvbN38" alt=""><figcaption></figcaption></figure>

Both flows cover the same launches: missions and Go To Location. The mechanical steps — selecting the mission or dropping the GTL marker, configuring parameters, working through the pre-flight checklist, hitting Launch, are the same in both. What changes is where the workflow lives on screen and what you can see while you work through it.

### Why the Panel Flow Matters for Mission Launches

The clearest operational difference shows up when launching a mission. In the Dialog flow, the embedded mini-map shows only the mission waypoints, stripped of every other map layer. You can see the path the drone will fly, but not what it will fly past, over, or near.

In the Panel flow, the main map handles the visualization. When you select a mission from the right panel, the map re-centers and zooms to the mission area while keeping every layer you already have on the map: no-fly zones, restricted areas, custom annotations, dock locations, other docked drones currently in the air. You're reviewing the mission against your actual operational picture, not a stripped-down preview.

<figure><img src="/files/0OPCwTdJT7ZgkH3ERizO" alt=""><figcaption></figcaption></figure>

For Go To Location launches, both flows behave similarly — you're already looking at the map when you drop the marker, so the mission-area zoom isn't relevant. The Panel flow simply moves the parameter configuration and checklist from the left panel (Dialog flow) to the right panel.

<figure><img src="/files/k47PEyKkxfH7pxAUJHWq" alt=""><figcaption></figcaption></figure>

### How to Switch

The launch flow setting is per-user. Each operator chooses their own preference; switching it doesn't affect anyone else on your team.

Path: Settings → General → Launch Flow

Two options:

* Dialog (existing flow)
* Panel (new flow)

<figure><img src="/files/spcJmUa0tx0arrDkFCbB" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Preference changes do not automatically apply to your current Operations session. After switching to **Panel View**, refresh the Operations dashboard (browser refresh, **F5**, or the reload button) for the new panel to take effect.&#x20;
{% endhint %}

### Defaults

* Existing users: Default remains Dialog. The Panel flow is available immediately — switch when you're ready.
* New users and new organizations: Default is Panel.

The Dialog flow will be retired in a future release. A specific timeline isn't set yet, but Panel is the direction the launch workflow is moving. Operators who switch now will be on the flow that's becoming standard.

#### Hardware Compatibility

Available for all dock types: Dock 1, Dock 2, and Dock 3.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://releases.flytbase.com/april-2026/see-your-mission-in-context-launch-flow-moves-to-the-side-panel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.