> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/dashboard-and-account/dashboard.md).
# Dashboard
[4. Dashboard, Portfolio and Activity](/tutorials/4.-dashboard-portfolio-and-activity.md) for a visual tour of its main views.
The dashboard is the home screen: portfolio value, realized P\&L, your active strategies, recent orders, alerts, and the entry point for creating a strategy.
### Stats tiles
| Tile | What it shows |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Portfolio value | Current market value of every strategy wallet (your connected browser wallet is excluded), from live wallet balances and pool prices |
| Today's realized P\&L | Sum of measured round trips closed today (UTC), with a measured/unmeasured coverage note |
| 30-day realized P\&L | Same, over 30 days |
| Trading KPIs | Order count, volume and fees, all-time and last 24 hours |
See [Profit and loss](/orders-and-transactions/pnl.md) for how these are computed and what they exclude.
### Active strategies
A sortable, filterable table (up to 8 rows) of running and paused strategies: type, name, status dot, pair, DEX's, P\&L, 24-hour volume, trade count, last activity, and **View** / **Pause** buttons. Stopped and completed strategies are not listed; find them on the list pages or under Archived.
The status dot combines the server's view with any pause you set locally in this browser — see [Managing strategies](/strategies/managing-strategies.md#pause-and-resume--what-actually-persists).
### Recent activity
The latest 20 orders with status, diagnosis for stuck orders, expandable details, Cardanoscan links and **Cancel & reclaim** where applicable. While any order awaits settlement the table refreshes every 15 seconds. See [Order statuses](/orders-and-transactions/order-statuses.md).
### Alerts
The alerts sidebar and system-health dots surface: strategy execution errors, arbitrage socket errors per strategy, unexpected pauses, a strategy wallet below 5 ADA, wallet balance lookup failures, strategy conflicts, and failed orders. Alerts are recomputed from live state; dismissing one hides it until the state changes again.
### Create a strategy
**New strategy** opens the type picker: Grid, DCA, Arbitrage, Rule-based, Cadence. Types not yet available are marked "Coming soon". `[VERIFY: the picker may show placeholder types that do not exist; confirm the list before publishing.]`
### Welcome tour
On first login a four-step tour (Overview, How it works, Your wallets, Safety) explains the non-custodial model and lets you try the Pause All button. `[VERIFY: whether it can be reopened later.]`
### Loading and errors
The dashboard shows a "Syncing markets" loader until stats, strategies and trades have all loaded; a slow trades query delays the whole page. Each of the three sources shows its own error toast if it fails; the rest of the page still renders.
---
# 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.surgecardano.com/dashboard-and-account/dashboard.md?ask=&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.
