> 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/sorting-and-column-layout.md).
# Sorting and column layout
## Sorting and column layout
Tables can be adjusted to the user's way of working. Most often, the user can sort data, change column order and select which columns should be visible.
### Sorting columns
Clicking a column header sorts data in ascending or descending order. Clicking the same header again may change the sort direction.
### Rearranging columns
1. Move the cursor over a column header.
2. Press and hold the left mouse button.
3. Drag the column to the selected position.
4. Release the mouse button.
5. If the screen supports saving layout, save the change.
### Selecting visible columns
If a screen supports column selection, the icon is usually above the table on the right side. After clicking it, the system opens `Selection of columns`.
1. Click the column selection icon.
2. On `Standard columns`, select the columns that should be visible.
3. In `Number of rows`, you can set the number of rows visible on the page if the screen supports this setting.
4. Click `SAVE`.
5. To return to default settings, click `RESTORE DEFAULT`.
6. The table shows only the selected columns.
### What to watch for
* Column layout changes may apply only to the current user or current view, depending on configuration.
* If data is missing after a change, check whether the required column was hidden.
* Not every table supports all column layout options.
### Related pages
* [Working with tables](/aquila-store-user-manual/system-basics/working-with-tables.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/sorting-and-column-layout.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.
