> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-dashboard/lct-add-widgets.md).

# LCT - Add Widgets

Device page > Widgets

Widgets are modular components of the IoT platform, designed to provide a flexible and dynamic way to visualize device data, monitor key metrics, and interact with operational features. These components allow real-time presentation of data through charts, tables, and device location visualizations.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd8qNBohR0mTTiHlhcGHSPI1OlBJOmzUscqUqa_VTlEaZxL9LzIgE57WIC6Cgm6C4nDncKOOGGIjZ9Y5ujrj6sBD79-J_NZTmsMkA3mC2ZStFkEMViCB31V4DyH8ncYsFCawOYeAA?key=Kl1KyU1gDzenB_F0xjN17rry" alt=""><figcaption><p>Add a Widget</p></figcaption></figure>

## **Steps to Find and Add Widgets**

1. Open the **Device Page** from the Cockpit menu.
2. Select the desired **device** to access its dashboard.
3. Click the **+ icon** on the dashboard to open the widget selection pop-up and choose the widget to add.


---

# 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.g-iot.io/low-cost-tracker-full-device-guide-book/low-cost-tracker-greater-than-giots-functions/lct-device-dashboard/lct-add-widgets.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.