> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/web-client/general/home-page.md).
# Home page
Access the aqua home page for quick entry to offerings, partners, products, support, and documentation. Learn how to configure default access or set your custom internal resources.
aqua home page
From aqua home page, you can get much easier access to all aqua offerings, partners and products. You can also find documentation or contact our customer support from there.
Public and private cloud users always have access to this page by default.
For on premise customers, it has also shown by default. But there is an option to configure it and enable your internal resources instead of aqua home page.
To enable your internal resources, the Server/System Administrator needs to modify the following keys in the aquaWebNG.config to:
{% hint style="info" %}
* AQUA\_HOME\_NEWSPAGE\_URL: *(your internal URL)*
* AQUA\_HOME\_NEWSPAGE\_IS\_WEBPAGE: true
{% 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.aqua-cloud.io/documentation/web-client/general/home-page.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.
