> 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/mandatory-base/platform-core/governance-and-monitoring/license.md).

# License

Under Settings -> *License*, you will find the BuildingPro Suites license. In BuildingPro Suites, the costs for using resources are measured in **Infravolts**, which function as a virtual currency. The display is divided into different areas:

In area **\[A]** **Infravolt Overview**, the **total number of Infravolts** included in the subscription, the currently **used Infravolts**, and the **available Infravolts** are displayed. This overview provides information about consumption and the remaining balance.

<figure><img src="/files/glPhP8RMfjuflm7IPljE" alt=""><figcaption></figcaption></figure>

**\[B] Packages:** The **Packages** section describes the subscription in detail, including the assigned Infravolts. If necessary, the subscription can be extended by uploading a new **license key**. To do this, you click on the corresponding button, select the license key file, and upload it. The expiration date of the subscription is also displayed, as well as a contact address for subscription adjustments.

**\[C] Infravolt Consumption:** The **Infravolt Consumption** area shows a detailed list of all components that consume Infravolts. **Connectivity** costs a one-time fee of 100 Infravolts for any number of connections. 10 Infravolts are charged for each user. The cost per asset depends on the number of linked attributes.

**\[D] Distribution of Assets:** In the **Distribution of Assets** section, the costs are broken down by **asset types**. Each asset type incurs costs based on the number and attributes of the respective assets.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/governance-and-monitoring/license.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.