> 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/who-this-documentation-is-for.md).

# Who this documentation is for

## Who this documentation is for

This documentation is intended for people who use the Aquila Flex backend in their daily work or are responsible for configuring data in the system.

### Main audience groups

| User group                  | When they use the documentation                                                                                    |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| System administrators       | When creating users, creating roles, granting permissions and configuring dictionaries.                            |
| Service desk                | When diagnosing user requests, checking permissions, locations, function visibility and common operational issues. |
| Head office employees       | When managing products, prices, promotions, locations, reports and central documents.                              |
| Store or location managers  | When reviewing documents, stock levels, orders, settlements and local reports.                                     |
| Operational users           | When performing specific tasks, such as creating a document, searching for a product or checking a report.         |
| Implementation team members | When training users and organising work processes.                                                                 |

### What this guide covers

The guide describes work in the backend user interface. It focuses on where to go, what to click, what to fill in, when to save data and what to watch for during common operations.

### What this guide does not cover

This part of the documentation does not describe:

* system installation,
* application server configuration,
* database configuration,
* technical integrations,
* source code,
* maintenance procedures outside the backend interface.

{% hint style="warning" %}
If a function is not visible in the menu, the most common reason is missing permissions or working in the wrong location.
{% 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/who-this-documentation-is-for.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.