> 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/logging-in.md).

# Logging in

## Logging in

Logging in starts work in the backend in the context of a selected location. The login screen may also allow the user to choose the interface language.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2FadCSXUWnsKx09d3PWudU%2F005.png?alt=media&amp;token=aa28cfbe-0bbc-4154-98bd-10ed3c4e4d91" alt=""><figcaption></figcaption></figure>

### When to use

Use this procedure at the beginning of work or after the session ends automatically.

### Steps

1. Open the backend address in a web browser.
2. If a language list is available on the screen, select the interface language.
3. In `Login`, enter the user name.
4. In `Password`, enter the user's password.
5. In `Location`, select or enter the work location.
6. Click `Log-in`.
7. If the data is correct, the system opens the home screen.

### Important fields

| Field    | Required                 | Description                                                                                                   |
| -------- | ------------------------ | ------------------------------------------------------------------------------------------------------------- |
| Login    | Yes                      | User name used for logging in.                                                                                |
| Password | Yes                      | Password assigned to the user account.                                                                        |
| Location | Yes                      | Location where the user starts work.                                                                          |
| Language | Depends on configuration | Interface language selected on the login screen. Available languages should be defined during implementation. |

### Incorrect login data

If the entered data is incorrect, the system displays a message on the login screen. In this situation, check:

* whether the login was entered correctly,
* whether the password is current,
* whether the correct location was selected,
* whether the user account is active,
* whether the user is allowed to log in.

Depending on configuration, the system may require a password change after the first login. If this message appears, follow the instructions shown by the system. If the login problem continues, contact the system administrator.

### Related pages

* [Backend access requirements](/aquila-store-user-manual/getting-started/backend-access-requirements.md)
* [Changing work location](/aquila-store-user-manual/getting-started/changing-work-location.md)
* [Changing password](/aquila-store-user-manual/getting-started/changing-password.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/logging-in.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.