> 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/preface/about-this-document.md). # About this Document ## Overview This document explains how to use **ABB Ability™ BuildingPro Suites**.\ It describes the platform structure, key capabilities, setup steps, and selected workflows for operating and configuring the system.\ The product connects building, energy, heating, ventilation, and air conditioning (HVAC), operational technology (OT), internet of things (IoT), and information technology (IT) data into one unified environment for building and portfolio management ## **Intended audience** * System integrators * Facility managers and operations teams * Real estate and portfolio operators * Service providers * Administrators who manage users, tenants, and roles This document is intended for users who work with ABB Ability™ BuildingPro Suites, including: ## **Permissions** Some functions described in this document are only available if the user has the required permissions. Access rights in ABB Ability™ BuildingPro Suites are controlled through **system roles** and **tenant roles**. If specific permissions are required for a task, they are stated in the relevant section. See [-> Roles](/collection/mandatory-base/platform-core/workspace-and-identity/roles.md) for details. --- # 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/preface/about-this-document.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.