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

# Data Room

The Data Room holds the materials investors read before they commit. You can protect it with an access code, and it logs who opened each file.

Investors open the room from the Invest page.

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

1. **Sub-tabs** Move between Documents, which holds the files investors can open, and Logs, which records who accessed them and when.
2. **Upload area** Accepts PDF, JPEG, PNG, DOC, and DOCX files of up to 100 MB each.
3. **Data Room Password** Sets an optional six digit code that investors enter before opening the room.
4. **Password field** Holds the code, with controls to reveal, copy, regenerate, or clear it.
5. **Documents table** Lists each file in the room with its name, type, and upload date.
6. **Row actions** Open, download, or delete a file from the end of its row.

### Access is logged

The Logs sub-tab records who opened each file and when, so you can see whether an investor has read the deck before a follow-up call.

### Password

When a password is set, investors enter a six digit code to open the room. The platform creates the code, and you can view it here at any time.

* **Reveal:** Shows the current access code on screen.
* **Copy:** Copies the code to your clipboard for sharing with investors.
* **Regenerate:** Issues a new code and retires the previous one.
* **Clear:** Removes the password, so anyone holding the deal link can open the room.

> **Regenerate replaces the code immediately.** Use it to reset access, for example after a colleague leaves, then share the new code with your investors. Keep a password on the room, because deal links can be forwarded.

### Upload limits

Export spreadsheet models to PDF before you upload them.

### **Data Room and Files**

* **Data Room:** The investor facing store, protected by the access code, logged, and opened from the Invest page.
* **Files:** The deal's internal store for your own working documents.

> If every investor should read a document, put it in the Data Room. If it is for your team, put it in Files.


---

# 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/data-room.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.