> For the complete documentation index, see [llms.txt](https://docs.kwenta.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kwenta.io/using-kwenta/perennial-isolated-margin/trading-on-perennial/futures-dashboard.md).

# Dashboard Overview

### Dashboard

Below, you'll find the main dashboard for Futures on Kwenta; from here, you'll get an overview of everything Futures, any open positions, and markets available to trade.

<figure><img src="/files/48oUcpgFjqQJR0ViP83f" alt=""><figcaption></figcaption></figure>

1. The menu section contains links to other pages inside of Kwenta.
2. Displays Current Portfolio value along with a chart over time
3. A quick overview of any open positions a trader currently has.
4. The Watchlist and be accessed here (controlled by what assets you have in your favorites)
5. An overview of any open orders


---

# 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.kwenta.io/using-kwenta/perennial-isolated-margin/trading-on-perennial/futures-dashboard.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.