> For the complete documentation index, see [llms.txt](https://user-help.runmags.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user-help.runmags.com/introduction/getting-in-and-navigating/user-interface.md).

# User interface

RunMags is designed with usability and a great user experience in mind. Although the system has many different functionalities, the user interface maintains the same consistent look no matter if you're in sales, production or finance.

![](/files/-M6CCoOB4TQIZwRnNN1U)

The interface is divided into five main areas:

1. Top bar which holds the RunMags logo, information on where in the system the user is currently working and the right hand menu for accessing profile, company and account setting.
2. The navigation menu to the left for navigating between the different tools available.
3. The main information window located top center where specific context like a client, a contract or a magazine is located. The final two areas display information related to the main information window.
4. Related information window (divided into tabs) located bottom center where related information to what's in context in the main information window is displayed, for example contacts related to a client company.
5. The sidebar window to the right that contains related information to what's in context but also can be manipulated in real time. For example if a client company is located in context, then a meeting booked in the calendar in the context menu will be related to that client company.

\
Most windows in RunMags can be expanded to simplify usage on tablets and even phones. At each boarder between the five main areas above, there are small triangles that can be clicked in order to minimize a specific area.


---

# 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://user-help.runmags.com/introduction/getting-in-and-navigating/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.