> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/simulation-control-monitoring-and-logging/interact-using-dashboards.md).

# Interact using Dashboards

## Introduction to Dashboards

Dashboards is an application, installed by default with RT-LAB, that provides an interactive environment for monitoring, tuning, and controlling real-time simulations.

**Dashboards connects to models through** **data points**, which are the interface between the simulation and the application. These data points include **parameters**, **control signals**, and **output signals**, and they define the values that Dashboards can read, display, or modify during execution.

The application offers **panels** for graphical visualization and control, as well as **tables** for viewing and editing variables. Users can monitor signals, adjust parameters on the fly, and create customized operator or testing interfaces. Changes made through Dashboards affect only the running simulation; the compiled model remains unchanged. This makes them well suited for safe experimentation and rapid iteration.

**Dashboards is the primary and recommended interface** for interacting with simulations. It provides a unified connection workflow, a modern UI, and support for multiple customizable **panels and tables** within a project.

<figure><img src="https://96827845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNRdpSk8kjn20gXAexnt6%2Fuploads%2Fgit-blob-71dfebf2d0e438b1e691609e8808918fa22f4dea%2FDH-overview.png?alt=media" alt=""><figcaption></figcaption></figure>

## **Requirements**

Dashboards requires a **built and loadable model** so that variables can be detected, mapped, and communicated in real time with the panels.

## Open Dashboards

In the RT-LAB **Project Explorer**, double-click **Dashboards** within your current project.


---

# 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://www.opal-rt.com/docs/rt-lab/simulation-control-monitoring-and-logging/interact-using-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.
