> 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/getting-started/changing-screen-layout.md).

# Changing screen layout

## Changing screen layout

The backend can be displayed in different visual variants. A user can change the interface theme and menu location if this configuration is available for the account.

**Menu path:** `Application -> Preferences`

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FxZAb6ULON6nuQ2TWOws5%2F010.png?alt=media&amp;token=f56eed64-0e51-4d7f-8838-9afda4c88a4c" alt=""><figcaption></figcaption></figure>

### When to use

Use this function when you want to adjust the backend appearance to your work style or restore the layout used in the documentation screenshots.

### Available settings

| Setting                  | Available values                                         | Meaning                                                                                    |
| ------------------------ | -------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| Theme                    | `Modern`, `Standard`                                     | Defines the visual theme of the system.                                                    |
| The location of the menu | `At the top of screen`, `On the left side of the screen` | Defines whether the system menu is displayed at the top of the screen or on the left side. |

### Steps

1. Open `Application`.
2. Select `Preferences`.
3. In `Theme`, select the interface theme.
4. In `The location of the menu`, select the menu location.
5. Save the settings using the operation available on the screen.
6. If required, refresh the page or log in again to see the changes.

### What to watch for

* All screenshots in this documentation are prepared for `Theme = Modern` and `The location of the menu = On the left side of the screen`.
* If the user selects another theme or top menu, function names remain the same, but element positions may differ from the screenshots.
* A detailed description of screen areas is available on [How to use this documentation](/aquila-store-user-manual/introduction/how-to-use-this-documentation.md).

### Related pages

* [How to use this documentation](/aquila-store-user-manual/introduction/how-to-use-this-documentation.md)
* [Changing work location](/aquila-store-user-manual/getting-started/changing-work-location.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/getting-started/changing-screen-layout.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.