> 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/backend-access-requirements.md).

# Backend access requirements

## Backend access requirements

The backend is a web application available through an internet browser. Aquila provides the login page address during project implementation. In many environments, connection to the company network or VPN is required before opening the application.

<figure><img src="https://4238787198-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqZBQT3Jc6WWk7SiGW9FZ%2Fuploads%2F98dynrlPQ5VEbx8OXkKn%2F004.png?alt=media&amp;token=dc51e100-4aaa-47ac-8243-58d4f8ac4e9a" alt=""><figcaption></figcaption></figure>

### When to use

Use this page before the first login and when diagnosing requests such as "I cannot open the login page".

### The user needs

| Element                       | Description                                                                                                                                                                                                                         |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Backend address               | The login page address provided by Aquila during implementation.                                                                                                                                                                    |
| Company network or VPN access | Required if the backend is not available from the public internet. VPN details and connection instructions are provided by the system administrator, IT department or the person responsible for implementation on the client side. |
| Internet browser              | A current web browser used to open the login page.                                                                                                                                                                                  |

### If the login page does not open

* First check internet access. Open another website, make sure the computer is connected to Wi-Fi or wired network, and then refresh the backend page. If other websites also do not open, contact local IT support.
* If the internet works, but after entering the address the page still cannot be opened, the reason may be missing VPN connection or environment unavailability. In this case, contact the system administrator.

### Related pages

* [Logging in](/aquila-store-user-manual/getting-started/logging-in.md)
* [Changing work location](/aquila-store-user-manual/getting-started/changing-work-location.md)
* [User roles in the system](/aquila-store-user-manual/introduction/user-roles-in-the-system.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/backend-access-requirements.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.