> 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/tips-and-tricks/hide-standard-header-and-footer-in-a-flow.md).

# Hide Standard Header and Footer in a flow

## Overview

Inside a screen flow, there is an option to deselect the navigation options. This page walks you through hiding the standard Header and Footer navigation for your screen flow.

{% hint style="info" %}
If you hide the footer but want to let the user navigate between screens, don't forget to add an action UI element like a [button](/flow/flow-components/button.md) to expose the actions.
{% endhint %}

## Steps

The steps to hide Standard Header and Footer are as follows:

1. Open your flow inside Flow Builder
2. Click on a screen flow and click on the "**`Edit Element`**" button
3. On the right panel, expand **`Configure Header`** and **`Configure Footer`**
4. Uncheck "**`Show Header`**" and "**`Show Footer`**"

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


---

# 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 dynamically by asking a question.

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

```
GET https://docs.avonnicomponents.com/flow/tutorials/tips-and-tricks/hide-standard-header-and-footer-in-a-flow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.