> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.12/development/flow-portal-2/getting-started/navigation.md).
# Navigation
## Settings
Select type to set the placement of the navigator. The type option are:
* Top: navigator shown above work area
* Side: navigator shown on the left-hand side of the work area
* Top/Side: navigator shown above and on the left-hand side of the work area
## Export / Import pages
Use the *Export* and *Import* buttons to export and import pages. Click *Export* and select the pages which are to be exported. More than one page can be exported at the same time.
To import, click the *Import* button. Browse to the file to import or drop the file in the allocated area.
{% hint style="info" %}
For information about imports from the old Portal, go to [Migrate existing solution](/6.12/development/flow-portal-2/getting-started-portal2.md#migrate-existing-solution).
{% endhint %}
## Tree
All pages can be managed via the page tree manager.
Using the page tree manager, users can:
* rearrange the order of pages
* create new pages
* delete existing pages
* search for existing pages
---
# 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://help.novacuraflow.com/6.12/development/flow-portal-2/getting-started/navigation.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.
