> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/reports/dashboard.md).

# Dashboard

Navigate to Dashboard

The dashboard page has customizable widgets that will allow a user to see summary reports at a glance.

Widgets can be added, removed, resized, and repositioned on the page. Each widget can be filtered by date and/or organization unit.

The page can be filtered by date/time range and/or by organization units. These controls are located on the top right corner. The page filters will not apply to widgets with custom filters.

| Widget                   | Description                                                                                                                                                                                                                                                                                                             |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Queue Interactions Chart | This report shows the total number of Interactions for your queues. This does not include direct calls. This chart can be helpful for seeing which queues are receiving the most or least interactions.                                                                                                                 |
| In Out Chart             | This report represents the total number of inbound and outbound interactions by your organization. If you have recording enabled, all interactions are being tracked including direct inbound/outbound calls.                                                                                                           |
| Leaderboard              | This report represents the agent with the largest interaction count (Total Inbound Direct Calls + Total connected interactions). The Average Handle Time is also displayed here. This can be helpful with getting an idea of which team member is handling the most interactions and finding their average handle time. |
| Call By Day Chart        | This report represents the total number of interactions in a day-by-day format. This gives you a snapshot of the interaction volume in a given period.                                                                                                                                                                  |
| Callback Requested       | This report represents the total number of contacts that have requested a callback.                                                                                                                                                                                                                                     |
| Queue Summary            | This report displays queue information, including total count, Abandoned count, and service level.                                                                                                                                                                                                                      |
| Agent Summary            | This report displays a visual representation of interactions handled by agents. More information can be found by hovering over a block.                                                                                                                                                                                 |

{% hint style="info" %}
If no data or not all data is shown on the charts, review the user's data access policies. See [Organization Units](/administration/organizational-units.md)
{% 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://cc.docs.landis.cloud/reports/dashboard.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.