# Navigation

Navigation is used to define the order of all pages displayed in the navigator. The navigator can have top-level and child-level entries with a maximum of three levels, creating a tree structure.

By default, the navigator is positioned at the side; however, an end-user option allows for switching between side and top orientations. Additionally, breadcrumbs can be enabled via end-user settings; this feature is off by default. The end-user settings are available under Profile > User Settings.

### Adding a new Page

* Create a new page in either the Portal or the Hub.
* Once the page name has been entered, the new page will appear at the top of the navigation tree. Drag and drop it to the desired placement.

### Change the navigation tree

In the DEV environment, an Admin user can see all pages in the portal within the navigation tree, regardless of whether they have editing access to the pages. This ensures there is a user role that can define the order of the entire navigation tree.

In Portal:

1. Go to Portal Settings > Navigation.
2. Drag and drop the pages to set the order. Note that only three levels are allowed.
3. Click Apply.

In Hub:

1. Open an application package, click the three-dot context menu on any portal page, and select Edit in Navigation.
2. Drag and drop pages to create the desired tree structure. Note that only three levels are allowed.

## TEST and PROD environments

The navigation structure in TEST and PROD is automatically inherited from DEV. When you deploy a page, the entire navigation tree structure is deployed with it.

Because not all pages exist in every environment, the structure adapts as follows:

* Missing Parents: If a child page is deployed but its parent is not, the child page will automatically move up one level to take the parent's place in the hierarchy.


---

# Agent Instructions: 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:

```
GET https://docs.novacura.com/flow-connect/reference/reference/portal/portal-settings/navigation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.