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

# System basics

## System basics

This chapter describes interface elements that repeat in many areas of the backend. They help users understand new screens faster and learn how to search, add, edit, delete, import and export data.

### What this chapter contains

| Page                                 | Purpose                                                         |
| ------------------------------------ | --------------------------------------------------------------- |
| System menu                          | How the side menu and work context work.                        |
| Filters and data search              | How to narrow result lists and search data.                     |
| Working with tables                  | How to read tables, pagination and result sections.             |
| Sorting and column layout            | How to sort and rearrange columns.                              |
| Lists, calendars and text search     | How to use selection lists, calendar and text search operators. |
| Data import and export               | How to export results and import data from a file.              |
| Adding, editing and deleting records | How basic record operations work.                               |
| System messages                      | How to interpret confirmations and warnings.                    |
| Document and record statuses         | How to understand saving, confirmation and editability.         |

{% hint style="info" %}
The available buttons may differ between screens, but their meaning remains consistent: add creates a new record, edit changes the selected record and delete requires confirmation.
{% 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/system-basics.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.