> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-2-system-administrator-manual/user_interface.md).

# User interface

The Boomerang Client user interface has the following elements:

![](/files/QAVahx86jy05P4bcwSuY)

1. Main menu.
2. Logout button.
3. System tree view.
4. Main window which by default shows the system overview which has two more bottom tabs showing active alarms. A smaller image of system overview is always shown in the left bottom corner. If a sensor is selected in the tree view then the sensor readings, chart and events are shown in this area. The detailed description of a sensor view is presented in chapter 7.

To return to system overview use “Menu – View – System status” or click small system overview in the left bottom corner.

At the top of the screen a system server address, its user defined name and main window contents title are shown.

The bottom bar presents the active user name, the interface language set and a current date and time.


---

# 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://help.boomerang3.com/boomerang-2-system-administrator-manual/user_interface.md?ask=<question>&goal=<endgoal>
```

`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.