> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/navigation/application/the-navigation-menu.md).
# Navigation settings (App)
This article explains how to customize the navigation menu in your Let's Get Digital app to create a tailored, intuitive experience for your attendees. You’ll learn how to configure which features app
### Where to change the App navigation
1. Go to your Admin Panel
2. Click on Navigation → Navigation Settings
### How to add a New Menu Item
1. Click on the button **Add new menu item**
2. Give the menu item a name
3. Choose where you want the page to link to
4. Save changes
### Strucuture your Menu
With a simple drag and drop system you can structure your menu. Simply click and hold on the menu item and drag to the desired section.
{% hint style="success" %}
You can find the tried and tested best practices that we reccomend using listed here: [**Go to best practices**](https://knowledge-base.letsgetdigital.com/the-admin-panel/navigation/application/pages/Xn52c7o7cU5hkzLbDgWy#id-1.-navigation-layout)
{% endhint %}
---
# 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://knowledge-base.letsgetdigital.com/the-admin-panel/navigation/application/the-navigation-menu.md?ask=&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.
