> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/navigation.md).

# Navigation

Step-by-step tutorials for the Avonni Navigation in Screen Flows, from building the menu items to tabs, multi-screen menus and record lists.

The Navigation puts a horizontal or vertical menu on a flow screen and tells the flow which item the user picked. These tutorials follow a service agent working one account: Overview, Contacts, Opportunities and Cases, without leaving the flow.

{% hint style="info" %}
New to the component? Start with [Build Tabs on One Screen with Navigation](https://docs.avonnicomponents.com/flow/tutorials/components/navigation/build-tabs-on-one-screen-with-navigation.md), then keep the [Navigation reference](https://docs.avonnicomponents.com/flow/flow-components/navigation.md) open for every property.
{% endhint %}

## Build the menu

Decide where the items come from and how they are grouped.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>New Navigation Item Collection</strong></td><td>Define the menu items once in a flow action and reuse them on every screen.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FNmK1zylT57lT29rzcy0X%2Fcover-new-navigation-item-collection.png?alt=media">cover-new-navigation-item-collection.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/actions/ui-and-navigation/new-navigation-item-collection.md">New Navigation Item Collection</a></td></tr><tr><td><strong>Add Sub-Menus and Columns to a Navigation Menu</strong></td><td>Group open and closed cases under one dropdown, with headings and columns.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FFLLhLQm4uIlEjAonKoiO%2Fcover-add-sub-menus-and-columns-to-a-navigation-menu.png?alt=media">cover-add-sub-menus-and-columns-to-a-navigation-menu.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/navigation/add-sub-menus-and-columns-to-a-navigation-menu.md">Add Sub-Menus and Columns to a Navigation Menu</a></td></tr><tr><td><strong>Build a Navigation Menu from a Picklist</strong></td><td>Turn Case Status values into a menu that follows the picklist, with counts on each item.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FcsilEus7BkBx8zm0ITM2%2Fcover-build-a-navigation-menu-from-a-picklist.png?alt=media">cover-build-a-navigation-menu-from-a-picklist.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/navigation/build-a-navigation-menu-from-a-picklist.md">Build a Navigation Menu from a Picklist</a></td></tr></tbody></table>

## Use the menu in a flow

Show a section, open a screen or display a record from the item the user clicks.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Build Tabs on One Screen with Navigation</strong></td><td>Show an account's Overview, Contacts, Opportunities or Cases on one screen, no Next click.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FsbQFi8i17AanW6MgDfTz%2Fcover-build-tabs-on-one-screen-with-navigation.png?alt=media">cover-build-tabs-on-one-screen-with-navigation.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/navigation/build-tabs-on-one-screen-with-navigation.md">Build Tabs on One Screen with Navigation</a></td></tr><tr><td><strong>Reuse One Menu Across a Multi-Screen Flow</strong></td><td>One side menu on every screen, and a Decision that opens the screen the agent picks.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FZTHclcomNQaCPh66s4Zn%2Fcover-reuse-one-menu-across-a-multi-screen-flow.png?alt=media">cover-reuse-one-menu-across-a-multi-screen-flow.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/navigation/reuse-one-menu-across-a-multi-screen-flow.md">Reuse One Menu Across a Multi-Screen Flow</a></td></tr><tr><td><strong>Building a Navigation Menu with Related Records</strong></td><td>List an account's open opportunities as a menu and show the one the agent clicks.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2F5elu7tRfJ44kDiKqlpr8%2Fcover-building-a-navigation-menu-with-related-records.png?alt=media">cover-building-a-navigation-menu-with-related-records.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/navigation/building-a-navigation-menu-with-related-records.md">Building a Navigation Menu with Related Records</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/flow/tutorials/components/navigation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
