> 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.md).

# Aquila Store - User Manual

## User Manual-Backend

This manual explains how to work in the Aquila Flex backend.

It focuses on daily user tasks, recurring screen patterns and the most important administrative operations.

### What this manual covers

The manual describes:

* logging in and starting work,
* moving around the interface and working with lists, filters and tables,
* managing users, roles and permissions,
* working with product records and product configuration.

### Who should use it

This manual is useful for:

* end users working in the backend,
* administrators managing users and permissions,
* service desk teams diagnosing access and data issues.

### Recommended reading order

If you are new to the backend, start with these chapters:

1. [Introduction](/aquila-store-user-manual/introduction.md)
2. [Getting started](/aquila-store-user-manual/getting-started.md)
3. [System basics](/aquila-store-user-manual/system-basics.md)

Then go to the task-specific chapters:

* [Users and permissions](/aquila-store-user-manual/users-and-permissions.md)
* [Products and product records](/aquila-store-user-manual/products-and-product-records.md)

### Chapter overview

| Chapter                                                                                   | Purpose                                                                               |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| [Introduction](/aquila-store-user-manual/introduction.md)                                 | Explains what the backend is, who uses it and how to work with the documentation.     |
| [Getting started](/aquila-store-user-manual/getting-started.md)                           | Covers access requirements, login, password change, logout and layout settings.       |
| [System basics](/aquila-store-user-manual/system-basics.md)                               | Explains filters, tables, lists, imports, exports and common interface behavior.      |
| [Users and permissions](/aquila-store-user-manual/users-and-permissions.md)               | Shows how to manage user accounts, roles and access scope.                            |
| [Products and product records](/aquila-store-user-manual/products-and-product-records.md) | Describes product data, product tabs, availability, prices and related configuration. |

{% hint style="info" %}
If a function described in the manual is not visible in the system, first check the user's permissions and current work location.
{% endhint %}

### How to use this manual

Use the table of contents to move by chapter, or open a task page directly when you already know what you need to do.

When a page includes a **Menu path**, start from that location in the backend and follow the listed steps.


---

# 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.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.