> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/streaming-integration/ui-overview/dashboard.md).
# Dashboard
## Live / Soon / Later
The Dashboard section is split into 3 sections:
* Live - Events that are currently live
* Soon - Events that are going to go live in the next few hours
* Later - Events that are going live later in the day, or in 4+ hours time
We've given priority to events that are live - these will be shown first in the Dashboard.
## Filter by Sport
You are able to filter the Dashboard for events within a certain sport, or within multiple sports.
You can set these by going to the "Add filter" button on the top right of the page, and selecting the sports you want to filter the Dashboard by:
## Notifications
Notifications are still sent to you via email, in the same way they always have been.
However, should you want to view all the notifications available to you, click on the bell icon in the top right of the page, and this will take you to the page where you can read all the notifications
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sportradar.com/streaming-integration/ui-overview/dashboard.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.