> 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/files.md).

# Files

The Files tab stores the deal's documents, filed by type. Open it to find a document or see which ones the vehicle still needs.

Files holds your own working documents, while the Data Room holds what investors read. You can also reach Files from Setup and from the Investors tab.

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

1. **Toolbar** Lets you filter by file type, refresh the list, or upload files.
2. **Type tabs** Show one kind of document at a time, such as the agreements or the tax letters.
3. **Column headers** Sort the table by any of its seven columns when selected.
4. **Type** Shows the kind of document chosen at upload, which decides the tab it appears under.
5. **Source** Shows whether the file was generated by the platform, uploaded to the deal, or added from Setup or the Investors tab.
6. **File name** Opens the document when you select its name.
7. **Delete** Removes the file from the deal.

### Files types

The type tabs include SPV Agreement, Subscription Agreement, Wire Instructions, Portfolio Wire Instructions, SS4, Financials, Resolution, and EIN Letter.

> The type tabs also work as a checklist. An empty tab shows a document the vehicle still needs. **File wire instructions under the right type.** Wire Instructions cover money coming into this deal, and Portfolio Wire Instructions are for investors.

### Source

Files come from three places: the platform when documents are signed, your own uploads, and Setup or the Investors tab. The Source column shows where each file came from.

### Changing a file

The file type is set at upload. To change it, delete the file and upload it again under the new type. If a file is out of view, check the number on the Filter button.


---

# 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/files.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.