> 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/platform/live-cockpit/widgets/predefined-widgets/donut.md).

# Donut

The Donut chart gives you an overview of the percentage shares of a whole.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fb1fOmXygv7tJsbDr8iY6%2FFrame%201010105805.png?alt=media&amp;token=d4a06b12-21d6-4afa-bb75-348f14924899" alt=""><figcaption></figcaption></figure>

## When should this widget be used?

When you want to see at a glance what percentage of a total consumption is used by individual devices.

## Configure Widget

{% @supademo/embed url="<https://app.supademo.com/demo/k-ITYKo5HqN5ga6Li6aW0>" demoId="k-ITYKo5HqN5ga6Li6aW0" fullWidth="true" %}

### Change the order of the displayed assets

You can adjust the order in which the assets are displayed in the Donut chart.

When creating assets: Use **\[A]** to drag and drop the individual assets into the desired order.

You can also make these settings afterward by using the [-> Edit widget option](https://docs.buildings.ability.abb/collection/platform/live-cockpit/widgets/operating-widgets.md).

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FP3CngAsUodZPCxNM2WiW%2FGroup%20679.png?alt=media&amp;token=7680d386-8364-4360-ba19-745a80b5e8bc" alt=""><figcaption><p>The order of the displayed assets can be changed.</p></figcaption></figure>


---

# 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/platform/live-cockpit/widgets/predefined-widgets/donut.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.
