> 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/hypersim/simulation-control-monitoring-and-logging/interact-using-dashboards/dashboards-menus-and-preferences.md).

# Dashboards Menus & Preferences

## Preferences

Click **File > Preferences** to configure settings for widget appearance, value formatting, and scaling of UI elements. Preferences are organized into three categories: **General**, **Simulation**, and **Logs**.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-415f5068cd42e03a8af03b4d6f110cf5aee70ddf%2FDH-preferences.png?alt=media" alt=""><figcaption></figcaption></figure>

### General <a href="#general" id="general"></a>

The **General** section lets you configure visual styles and overall appearance settings across the entire application. Dashboards support two theme palettes, **Light** and **Dark**, while widgets with custom colors remain unaffected. Default value formatting for decimal numbers can be set to **Automatic**, **Floating Point**, or **Scientific**, with significant digits adjustable manually. The default scale font size for widgets displaying scale-based values, such as knobs, gauges, sliders, thermometers, and graphs, can be set to **Small (10)**, **Medium (12, default)**, or **Large (14)**.

### Simulation <a href="#simulation" id="simulation"></a>

The **Simulation** section defines how the application handles parameter values at the end of a simulation. By default, **Always ask at the end of a simulation** is enabled, prompting you to either **Discard** or **Keep changes** when pressing the stop button. **Keep changes** preserves any edits made during the simulation, which can still be reverted later to the default values. **Discard changes** resets all parameters to their values before the simulation started.

### Logs <a href="#logs" id="logs"></a>

The **Logs** section provides access to all log messages. Click the **Open Logs** button to open the log files in Windows Explorer. This makes it easy to review messages or send a detailed report to OPAL-RT support if issues arise.

## View

Click **View** to access quick settings:

### Themes

Choose from available themes to change the UI style to your preference.

### Zoom

Zoom in, zoom out, or reset the zoom for the entire application.

### File Manager

The File Manager shows all files accessible within the current project. Using the context menu, any file can be replaced, which updates all occurrences of that file in the project. File visibility depends on location: a file may be available only in the current project or across the entire workspace. Shared files cannot be deleted or replaced.

<figure><img src="https://3623212549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLxgTpoh7kyPmQ5vuyqD7%2Fuploads%2Fgit-blob-97e759bad4efb8d604046c54a95bbcaf25cee238%2FDH-file-manager.png?alt=media" alt=""><figcaption></figcaption></figure>

**Stay on Top**: Keeps Dashboards windows above all other Windows applications.

All selected **View** settings are retained when reopening the Dashboards application.

## Help

The **Help** menu includes: About, Documentation, Retake Tour, Shortcuts, Give Feedback, Contact OPAL-RT Support, and License.


---

# 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/hypersim/simulation-control-monitoring-and-logging/interact-using-dashboards/dashboards-menus-and-preferences.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.
