> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/understand-your-business/widget-configuration/widget-views.md).
# Widget Views
Switch between Summary and Detail view.
There are currently two display modes for your widgets located on the **Dashboard** page: [**Summary**](#summary-view) and [**Detail**](#detail-view) views. You can toggle between these widget views from the top-right area of any widget:
**Note:** Widget views are only available for widgets with numerical data. For example, you cannot select a widget view for a Camera Group widget. You can however select a widget view for a Report widget.
### Summary View
Summary view displays the total sum of the data in a widget. For example, if the widget tracks the number of transactions across all of your locations for a given week, Summary view provides you with the total sum of all transactions for that week. If you are comparing two different time periods (this week vs last week) the sum from each week is displayed in this view.
See the image below for an example of a widget in **Summary** view. This example widget also displays two different time periods (this week vs last week):\
### Detail View
**Detail** view displays the graph type for the widget. For example, if you selected a bar graph or line graph during the widget creation process, data is displayed relative to the selected graph type in **Detail** view.
See the image below for an example of a widget in **Detail** view:
### Expand Widget/More Details
Select the "i" icon to expand the widget and reveal more information:
---
# 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://help.solink.com/docs/understand-your-business/widget-configuration/widget-views.md?ask=&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.