> 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/introduction.md).
# Introduction
## Introduction
The Aquila Flex backend is the part of the system used to manage operational, administrative and commercial data for a retail network. In the backend, users work with product records, users, roles, locations, price lists, promotions, warehouse documents, settlements and reports. This documentation is task-oriented and is intended for end users, administrators and service desk teams. This means that users do not need to know the full menu structure before they can complete a specific task. The chapters guide users through common operations such as adding a user, editing a product, changing a price, creating a promotion or searching for a document.
### What this chapter contains
| Page | Purpose |
| ------------------------------- | ------------------------------------------------------------------------- |
| What is the Aquila Flex backend | A short explanation of the backend's role in operational work. |
| Who this documentation is for | Information about who should use this guide. |
| User roles in the system | Main user groups and their areas of responsibility. |
| How to use this documentation | How to read pages, menu paths, screenshots and step-by-step instructions. |
| Glossary | Definitions of the key terms used in the system. |
{% hint style="info" %}
This documentation describes how users work in the backend. It is not technical documentation for the application code or server administration.
{% 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://docs.aquiladynamics.com/aquila-store-user-manual/introduction.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.
