# Workflow

### Overview

Workflow refers to the collection of states that a story can be in. Avion is very flexible with custom workflow configurations, allowing you to define a workflow that fits your team. Our backlog integrations also support very flexible mapping of your workflow states, meaning that you are not fixed into using the same workflow in Avion as in an integrated backlog tool.

Workflow is spread across three main categories — *To do*, *Doing* and *Done*. These are not configurable. However, within each category, you can add as many states as you want.

{% hint style="info" %}
Each state category needs a minimum of one state. So the simplest workflow setup might be To do, Doing and Done (one state per category, named the same as the category).
{% endhint %}

You can customise the workflow per story map by heading to **Settings** → **Manage workflow**, as shown below.

![](https://3578170569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL6HR00hwiJJav4pLph%2Fuploads%2F73g9fFbQgfYc8RcZn3uy%2Fworkflow.jpg?alt=media\&token=25e6f9ca-1f0c-42d3-af88-c71a19fae2ae)

With the above workflow, the story state selector would show:

![](https://3578170569-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LL6HR00hwiJJav4pLph%2Fuploads%2FX0I2VOVwxY2nKZYpImTZ%2Fstory-states.jpg?alt=media\&token=089e5baa-beb2-4278-a48e-d30579686b85)

### Edit workflow

You can change your workflow at any time, which includes when workflow states are mapped to a backlog integration state. Just be aware that integration state mappings are managed from the integration configuration panel.

### Best practice

* Avion is for planning, so it makes sense to outline your planning workflow in the *To do* and *Doing* state categories.
* Some planning state examples:
  * Awaiting wireframes
  * Awaiting creative / designs
  * Awaiting legal
  * Needs content writing
  * Needs tech sign-off
  * Ready for development
  * In development
  * In user acceptance testing
  * Ready to deploy


---

# 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://help.avion.io/docs/story-map/workflow.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.