> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-ui-builder/areas/sections/summary-dashboards.md).

# Summary Dashboards

Configuring a summary dashboard to provide an overview of collections within a section.

A summary dashboard appears automatically at the root of an Umbraco UI Builder section. It provides an overview of key collections within that section, enabling quick access to list views. Additionally, it allows for adding new entries to the collection, provided the collection is not set to read-only.

By summarizing important data and simplifying navigation, the summary dashboard improves content management efficiency.

![Summary Dashboard](https://1288621994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPNKg2acg7Sia2MOol0UX%2Fuploads%2Fgit-blob-6e7f09e3d8b2933b5c880f0b0f20c95f3a984250%2Fdashboard%20\(1\).png?alt=media)

## Displaying a Collection on the Summary Dashboard

To display a collection on the summary dashboard, use the `ShowOnSummaryDashboard()` method in the collection configuration.

### Configuration Example

```csharp
collectionConfig.ShowOnSummaryDashboard();
```

**Code Reference:** `ShowOnSummaryDashboard() : CollectionConfigBuilder<TEntityType>`

{% hint style="warning" %}
Only root-level collections within a section can be displayed on the summary dashboard.
{% endhint %}


---

# 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.umbraco.com/umbraco-ui-builder/areas/sections/summary-dashboards.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.