> For the complete documentation index, see [llms.txt](https://docs.dunedocker.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dunedocker.app/dune-docker-console/overview.md).

# Console Overview

The browser Console is organized into three groups.

| Group              | Pages                                                                                            |
| ------------------ | ------------------------------------------------------------------------------------------------ |
| Server Operations  | Home, Server Control, Backups, Database, Updates, Logs, Settings                                 |
| Arrakis Management | Maps, Players, Guilds, Bases, Vehicles, Exchange, Live Map, Landsraad, Admin Tools, Care Package |
| Community          | Addons                                                                                           |

**Home** is the best starting point for current health, readiness, version information, server actions, and first-run status. Other pages focus on a single responsibility and show confirmations before disruptive or destructive actions.

## Important Behavior

* Buttons that change game data are audited and protected by the Console's authorization policy.
* Some game-data changes require a player to be offline; the relevant action tells you when this is required.
* Some map configuration changes require only Overland or affected map instances to restart. Read the confirmation text before applying.
* Safety-sensitive database actions create a labeled backup automatically.
* Long-running operations remain visible as tasks and report their final result.

{% hint style="info" %}
Prefer the guided Console for daily work. The CLI remains available for automation, recovery, and advanced troubleshooting.
{% endhint %}


---

# 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://docs.dunedocker.app/dune-docker-console/overview.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.