> For the complete documentation index, see [llms.txt](https://uni.fotello.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uni.fotello.co/orders/orders-dashboard.md).
# Orders Dashboard
The **Orders Page** helps you track new bookings or log orders manually. To access this, click **Orders** in the left sidebar.
The page opens on two tabs: **Orders** for your bookings, and **Invoices** for every invoice you have raised. Switch between them at the top of the page. See [Order Invoices](/payments/order-invoices.md).
If your customers book through your [Order Form](/orders/order-form.md), the orders show up here automatically. When status appears as **Pending,** you can click to review all the information and accept or cancel it**.**
{% hint style="info" %}
In the **Orders**, **Invoices**, **Listings**, **Customers**, and **Customer Teams** tables, Command-click or Ctrl-click a row to open it in a new tab. You can also middle-click a row.
{% endhint %}
{% hint style="info" %}
If you have turned on auto-accept orders in **Order Form → Settings**, the status will show **Accepted** by default.
See [Order Settings](/orders/order-settings.md).
{% endhint %}
### Cancel an accepted order
You can cancel an order after accepting it.
1. Open the order.
2. Click the **⋯** menu in the upper-right corner.
3. Select **Cancel**.
If you need help canceling an accepted order, contact support for assistance.
---
# 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://uni.fotello.co/orders/orders-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.
