> 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/calendar.md).

# Calendar

The Calendar widget displays the status of a selected asset distributed over a day. The Calendar widget is specially designed to show the utilization of rooms.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2FEhvyiTLI59njKXqTyBJl%2FGroup%20677.png?alt=media&amp;token=c1a58aa2-daf3-4787-a89a-0cc387f66c50" alt=""><figcaption><p>The Calendar widget.<br>From top to bottom: Day view, week view, month view</p></figcaption></figure>

## Operation

<div data-full-width="true"><figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2F54G5KyGUKBXnf5lKr14N%2F1F3DE6F7-53D9-44AF-85E5-544F911247B6.png?alt=media&#x26;token=a814a630-de01-4736-9c94-b6a4d43e1e2a" alt=""><figcaption><p>Month display</p></figcaption></figure></div>

<table data-full-width="true"><thead><tr><th width="63.133321126302064"></th><th width="150.4000244140625"></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Widget title</td><td>Title of the widget. Is influenced by the selection of the "Primary Asset."</td></tr><tr><td><strong>[B]</strong></td><td>Icon</td><td>Icon of the widget</td></tr><tr><td><strong>[C]</strong></td><td>Entry</td><td>Times that are considered "occupied" are highlighted as an entry in the widget.<br>Move the mouse over an occupied entry to see details.</td></tr><tr><td><strong>[D]</strong></td><td>Total time</td><td>The total time the room was occupied on a day. Note: This value also includes times that are outside the displayed period.</td></tr><tr><td><strong>[E]</strong></td><td>Day</td><td>Name of the weekday</td></tr><tr><td><strong>[F]</strong></td><td>Set scale</td><td>Click to choose whether a day, a week, or a month should be displayed.</td></tr><tr><td><strong>[G]</strong></td><td>More options</td><td>See -> Widget Options</td></tr></tbody></table>

### Display details

Move the mouse over a calendar entry to see more details about the corresponding entry.

<div data-full-width="true"><figure><img src="https://3489494878-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9GvUpaatBiReR43XFSMg%2Fuploads%2FIByLd9EDAyShpEAk8jKF%2FECE9845D-5FEA-42C4-865C-428B63A27195.png?alt=media&#x26;token=4a56e9cb-c4cf-4700-b244-eac07ee13a9d" alt=""><figcaption><p>When the mouse is moved over an entry in the calendar, the entry is highlighted and details are displayed.</p></figcaption></figure></div>

## Configuration

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

1. Make sure you are in the "Dashboard" menu
2. Click on "Add widget"
3. Click on "View"
4. Click on "Calendar"
5. Select the primary asset. The name of this asset will appear in the title bar of the widget.
6. Under "Room Asset," select the asset that you want to link with the "Calendar" widget.
7. Specify whether the whole week or only weekdays should be taken into account in the widget.
8. Specify the start and end time. The time between the two values is displayed in the widget.
9. Choose whether the current value or the aggregated value should be displayed.
10. Optional: Select how much space the widget should occupy on the dashboard.
11. Click on "Add widget"


---

# 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/calendar.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.
