> For the complete documentation index, see [llms.txt](https://wiki.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.roaddirect.co.nz/eboard/dashboard.md).

# Dashboard

The Dashboard is where office staff manage jobs that need work before or outside the Calendar: incoming requests from the Job Booking Portal, TMPs that need preparing, quotes, jobs without confirmed dates, and lists of all, archived and deleted jobs.

Open it from the **Dashboard** icon in the eBoard navigation bar. The Dashboard is available to users with an access level higher than [Basic User](/getting-started/user-access-levels.md#basic-user).

## Tabs

| Tab                                                             | What it's for                                                                           |
| --------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| [TMP Dashboard](/eboard/dashboard/tmp-dashboard.md)             | Incoming booking requests, draft jobs, and jobs grouped by where their TMP is up to.    |
| [Jobs To Quote](/eboard/dashboard/jobs-to-quote.md)             | Incoming quote requests and quotes being prepared or sent.                              |
| [Dates Not Confirmed](/eboard/dashboard/dates-not-confirmed.md) | Jobs without booked dates, grouped by when they're expected.                            |
| [TMP Only](/eboard/dashboard/tmp-only.md)                       | Jobs where you're only preparing a TMP.                                                 |
| [Dry Hire and Misc](/eboard/dashboard/dry-hire-misc.md)         | Dry hire jobs, and jobs with the Misc job type.                                         |
| **All Client Requests**                                         | Every request received through the [Job Booking Portal](/eboard/job-booking-portal.md). |
| [All Jobs](/eboard/dashboard/all-jobs.md)                       | Every job, of every type.                                                               |
| [Archived](/eboard/dashboard/archived-jobs.md)                  | Archived jobs.                                                                          |
| [Deleted](/eboard/dashboard/deleted-jobs.md)                    | Deleted jobs, which you can undelete.                                                   |

## Common features

* **Add Job** (green **+**) and **Add Callout Job** (red truck) at the top right. See [Book a job](/eboard/book-a-job.md).
* **Tutorial Video** link.
* **Job Booking Portal**: opens your portal; use the button next to it to copy the link.
* **Export to Excel**: downloads the list.
* Lists are split into **groups** with a count. Click **+** to expand a group.
* Click a column heading to sort, and type in the boxes under the headings to filter.
* Some tabs have an **Include complete jobs** option to show finished jobs as well.
* Every job has a **⋮** menu with actions such as **View Job**, **Email** and **View In Tracking**. Other actions depend on the tab and group, and are described on each tab's page.

{% hint style="warning" %}
If you see a **Create 10 Random Jobs** button, it creates dummy test jobs. Don't use it in your live organisation.
{% 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://wiki.roaddirect.co.nz/eboard/dashboard.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.