> For the complete documentation index, see [llms.txt](https://docs.lowcoder.cloud/lowcoder-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lowcoder.cloud/lowcoder-documentation/build-applications/app-editor/visual-components/layout-and-navigation/navigation.md).

# Navigation

In Lowcoder, the **Navigation** component enables the creation of multi-screen applications with structured menus, enhancing user experience through organized access to various app screens. 

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

**Key Features:**

1. **Menu Creation:** Design hierarchical navigation menus for desktop applications and flat navigation structures for mobile apps, accommodating different user interface requirements.&#x20;
2. **Dynamic and Static Menus:** Construct menus manually or generate them dynamically using data queries, providing flexibility in menu management.&#x20;
3. **App Integration:** Aggregate multiple app screens into a cohesive, multi-page application, allowing seamless transitions between different sections.&#x20;
4. **Customisation:** Tailor menu items by selecting associated apps, customizing labels, and choosing icons to align with the application's design and functionality.&#x20;
5. **Submenu Support:** For desktop applications, create nested submenu items to establish a clear hierarchy within the navigation structure.&#x20;
6. **Parameter Passing:** Append URL query or hash parameters to menu items, enabling the transfer of specific data or states between app screens.&#x20;
7. **Permissions Management:** Control the visibility of menu items based on user permissions, ensuring that users only access authorised sections of the application.

### Component Playground

On Component Playground, you can interact with the Modal component and explore it's Properties, Events and Methods. Play with different Styling properties to see the effect on the Modal component.

{% embed url="<https://app.lowcoder.cloud/playground/navigation/1>" %}

### Component Auto-Docs

In the Auto-Docs of Modal component, we have shown how to use different properties of the Modal component. It also includes the Styling properties of the Modal component.

{% embed url="<https://app.lowcoder.cloud/components/navigation>" %}

#### Properties of the Navigation <a href="#properties-of-the-table" id="properties-of-the-table"></a>

These properties are accessible in {{ }} notations, as well as in JavaScript Queries.

<table><thead><tr><th width="176.38671875">Property Name</th><th width="114.9921875">Type</th><th>Description</th></tr></thead><tbody><tr><td>hidden</td><td>Boolean</td><td>Returns True or False based on whether the Navigation component is hidden or not</td></tr><tr><td>items</td><td>Array</td><td>Returns Array of Objects containing the items in the Navigation component</td></tr><tr><td>logoURL</td><td>String</td><td>Returns the URL of the Logo placed in the Navigation component</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 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.lowcoder.cloud/lowcoder-documentation/build-applications/app-editor/visual-components/layout-and-navigation/navigation.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.