> For the complete documentation index, see [llms.txt](https://docs.aquiladynamics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aquiladynamics.com/aquila-store-user-manual/system-basics/system-menu.md).

# System menu

## System menu

The system menu is a permanent backend element. In the layout used in this documentation, it is on the left side of the screen and leads to the main work areas.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FLFyKmDRDDvnoNi4Dwdbw%2F003.png?alt=media&amp;token=34590915-260a-4111-b4ed-435ca53438dc" alt=""><figcaption></figcaption></figure>

### When to use

Use this page to understand where work with a module starts and how to identify the current user context.

### Main screen elements

| Element            | Description                                                                                                              |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| System menu        | Side menu with the main system areas, such as `Documents`, `Reports`, `Settlements`, `Administration` and `Application`. |
| Login details      | Information about the logged-in user, current location and open screen.                                                  |
| Main area          | The main part of the screen where the user reviews data, fills in forms and performs operations.                         |
| Filter / form      | A form or filter section where the user enters criteria or data required for an operation.                               |
| Data/results table | A list of records or items matching the search criteria.                                                                 |
| Tabs               | Additional detail sections visible on selected screens, such as document items, prices or attributes.                    |
| Action buttons     | Buttons used to perform operations, such as add, edit, delete, save, confirm or print.                                   |

### How to use

1. Select a main area in the menu, such as `Documents`, `Reports`, `Settlements`, `Administration` or `Application`.
2. Expand the next menu levels.
3. Open the correct screen.
4. Check the user and location in the upper-right corner to make sure you are working in the correct location.

### What to watch for

* The menu may show only functions available for your permissions.
* If a function is missing, check the user role and work location.
* If you work in another interface layout, the menu position may differ from the screenshot, but function names remain the same.
* The `Back` option may appear in the menu after a screen is opened and lets the user return one level.

### Related pages

* [Changing screen layout](/aquila-store-user-manual/getting-started/changing-screen-layout.md)
* [User roles in the system](/aquila-store-user-manual/introduction/user-roles-in-the-system.md)


---

# 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://docs.aquiladynamics.com/aquila-store-user-manual/system-basics/system-menu.md?ask=<question>&goal=<user_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.