> 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/documentation/einstellungen/lizenz.md).

# License

## license

Under Settings -> *license* you will find the Eliona license. In Eliona, the costs for the use of resources are measured in **Infravolts** measured, which serve as a virtual currency. The display is divided into different areas:

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

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/KAkz7cPwRZzmRdGqoaXj/Lizenz%20(1).png" alt=""><figcaption></figcaption></figure>

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

**\[C] Infravolt Consumption:** The section **Infravolt Consumption** shows a detailed list of all components that consume Infravolts. The **Connectivity** costs a one-time 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] Asset Distribution:** In the **Asset Distribution** the costs are broken down by **asset types** broken down. 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 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/documentation/einstellungen/lizenz.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.