> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/getting-started/willkommen-in-abb-buildingpro-eine-interaktive-einfuhrung.md).
# Welcome to ABB BuildingPro: An interactive introduction
## **Onboarding in** ABB BuildingPro
The **onboarding feature** in ABB BuildingPro offers new users an interactive tour of the platform's key functions and modules. As soon as you enter a page for the first time, you will be shown a brief introduction that explains the main functions of this page.
**Onboarding features:**
* **Step-by-step tour**: You can navigate through the various explanations of a page's functions by clicking **“Next”** click.
* **navigate back**: If you want to read an explanation again, you can **“Back”** to return to the previous step.
* **Skip**: If you do not need the introduction, you can end the onboarding with **“Skip”** finish.
{% hint style="info" %}
The onboarding is displayed **only once** per page. If you end the onboarding with **“Skip”** it will no longer be shown to you on this page in the future.
{% 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.buildings.ability.abb/collection/english-v14/getting-started/willkommen-in-abb-buildingpro-eine-interaktive-einfuhrung.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.
