> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/naviga-dashboard-overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/naviga-dashboard-overview/dashboard-5/user-guide/getting-started.md).

# Getting started

## Device support:

Naviga Dashboard is developed to run on desktop. To some extent it will also work on a tablet, but this is not actively developed or tested. 

## Browser support

The official browser supported is Google Chrome. 

There is unofficial support for several Browsers; for example Mozilla Firefox, Apple Safari. These browsers are not tested, and we know there are issues with the UI in some of these browsers. See these browsers as a fallback in the case Chrome would push out an update that is problematic.

## Screen resolutions

The minimum resolution for Naviga Dashboard is 1440px .The recommended resolution is however 1680px.\
This includes an article list and Writer in Dashboard. Having many applications open may result in screen space not being enough. 


---

# 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.navigaglobal.com/naviga-dashboard-overview/dashboard-5/user-guide/getting-started.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.