> For the complete documentation index, see [llms.txt](https://docs.allocations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allocations.com/why-allocations/deals.md).

# Deals

The Deals screen lists every vehicle in the Funds workspace and is the quickest way to find one deal by its name, type, or status.

The Dashboard and this page list the same vehicles in the same nine columns. The Dashboard adds three portfolio summary cards for a daily review, while this page adds search and filters for finding a specific deal.

![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/RrZTak9MLHrtmpLeFAO8/Unknown%20image)

1. **Total deals:** Counts every deal in the workspace, including drafts and test vehicles.
2. **Search deals:** Finds a deal by typing any part of its name.
3. **Filter** Opens the filter panel, with the number of conditions applied in brackets.
4. **Status filters:** Filter the table by deal stage, so one filter shows every deal at that stage.
5. **Type row** Limits the table to one vehicle type: All, SPV, FUND, or Migration.
6. **Toolbar:** Lets you refresh the table, export it, or create a new deal.
7. **Total Signed and Total Wired** Show what investors have committed to each deal and how much of that money has arrived.
8. **Actions** opens the deal on its Overview tab, where the raise and its outstanding work are summarized.

### Filtering

Use search, Filter, the status filters, or the type row to show fewer deals in the table. You can combine them, such as searching for a name while a status filter is selected.

> If a deal you expect is out of view, check the number on the Filter button and clear any filter left from an earlier session. Export follows your filters, so clear them when you want every deal in the file.

The type row and the status filters work separately, so check both when the table looks filtered.

### Opening a deal

Select Actions at the end of a row to open the deal on its Overview tab, described in **The Overview tab**.


---

# 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.allocations.com/why-allocations/deals.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.