# Navigation

The primary navigation is, of cause, the main menu with its second level navigation (1). Another common navigation is lists in views (3) and tabs in top of panels (2). If beneficial for the end user, you can also have navigation inside a panel (4).

![Illustration of the four different navigation areas.](/files/-M3fVGcKPrrTt1AJk7J7)

| Area                        | Description                                                                                                                                    |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Main menu, first level (1)  | This is for main sections (not individual views) and groups multiple related views/apps. This menu item has an icon.                           |
| Main menu, second level (1) | This is the sub sections or specific views of the first level main menu. This menu item has an icon.                                           |
| Main menu, third level (1)  | The is more rarely used but can be efficient for providing a kind of shortcut to functions or "latest used" items. This menu item has no icon. |
| Tabs (2)                    | This is for shifting between content in the same panel. Has no icon.                                                                           |
| Lists (3)                   | <p>Often presented in tables with links. This guides the user to items or other areas in the application. Most often this have no icon.        |

</p><p>Can also be used as a "split view" navigation, where clicking the link will present new content on a part of the page.</p> |
| Navigation panel (4)        | Be cautious – making too much navigation, can be confusing to the end user. Less is more. However, a navigation panel inside a pane gives room more options.                                                                                                               |


---

# 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://dev.xena.biz/xena-developer/user-interface/styleguide/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.
