> For the complete documentation index, see [llms.txt](https://knowledge.rollcredits.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.rollcredits.io/project-dashboard/project-dashboard.md).
# View the project dashboard
See a production's budget, card spending, invoice payments and vendor W9s at a glance on the Project Dashboard.
The Project Dashboard sums up the current production on one page. Owners, Super Admins and Managers open it from **Project Dashboard** in the sidebar.
{% hint style="info" %}
If your company uses the Project Dashboard, it's in the sidebar for those roles. Otherwise, it doesn't appear.
{% endhint %}
Under the **Dashboard** heading and the production's name are up to four summary cards. Select a card's title to open the full page behind it. Amounts are in US dollars, with other currencies converted.
## Budget
The **Budget** card sums up the production's first budget, the first tab on **Budget & Cost Report**. Select **Budget** to open that page.
* **Total**: **Paid** plus **Pending**.
* **Paid**: approved spending that has been paid.
* **Pending**: spending that isn't approved or isn't paid yet, plus estimates that aren't on a purchase order.
* **Budgeted**: the budget's first phase, plus any Approved Overages phases.
The bar under **Total** fills with Paid, then Pending. When Total passes Budgeted, the bar is full and a warning dot marks where the budget ran out. With no budget or no phases, every amount is zero. See [Track your budget](/budget-and-cost-report/budget.md).
## Card Program
{% hint style="info" %}
You see this card only if your production uses RollCredits cards.
{% endhint %}
The **Card Program** card sums up the transactions on the **P-Card** tab of **Transactions**. Select **Card Program** to open **Cards**.
* **Spend Total**: the total of those transactions.
* **Total Transactions**: how many there are.
* **Receiptless Transactions**: how many still have no receipt. Ones with **No file to upload?** ticked aren't counted.
## Invoice Payments
Only Owners and Super Admins see the **Invoice Payments** card. Select **Invoice Payments** to open the **Vendors & Contractors** tab of **Transactions**.
The card sorts that tab's transactions into four groups, each with a total, such as **Paid Total**, and a **# Transactions** count. Point at a group to see what it counts.
| Group | What it counts |
| -------------- | ---------------------------------------------------------------------------------- |
| **Paid** | Payments that reached the vendor, and invoices marked as paid outside RollCredits. |
| **In Process** | Payments on their way to the vendor. |
| **Unclaimed** | Scheduled payments, and sent payments the vendor hasn't accepted yet. |
| **Unpaid** | Invoices and estimates with no payment. |
To pay an invoice, see [Pay vendor invoices](/transactions/transactions/pay-invoices.md).
## Vendors
The **Vendors** card counts the vendors on this production's transactions. Select **Vendors** to open the **Vendors** tab of **Project > Vendors & POs**.
* **Total**: all of those vendors.
* **With W9**: vendors with a W9 on file.
* **Pending W9 Request**: vendors asked for a W9 who haven't sent one yet.
* **Missing W9**: vendors with no W9 and no request.
To request or add a W9, see [Collect W9s from vendors](/project/vendors-and-pos/vendor-w9s.md).
---
# 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://knowledge.rollcredits.io/project-dashboard/project-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.
