> 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/fund-manager.md). # Fund Manager The Dashboard is the first screen in the Funds workspace. It brings together your deals, investors, and portfolio, so it is the place to start every day. ![](https://content.gitbook.com/content/9IirLidzibYpEfSBave3/blobs/IVvN0pqCyFHpTKMSp622/Unknown%20image) 1. **Workspace switcher:** Switches between Portfolio, Funds, and Entities, and changes the whole sidebar below it. 2. **Summary cards:** Show Asset Under Management, Total Investors, and Total Deals across your whole portfolio. 3. **Filter** Opens the filter panel, with the number of conditions applied in brackets. 4. **Status filters:** Filter the table by deal stage, from Draft to Test. 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. ### The three summary cards The three cards cover your whole portfolio: the capital you manage, your investors, and your deals. * **Assets Under Management:** The capital you manage across every vehicle, shown with a quarter-over-quarter trend. * **Total Investors:** The number of investors across all vehicles, counting someone invested in three deals once. * **Total Deals:** Every deal in the workspace, including drafts and test vehicles. > These cards show totals for your whole portfolio. The deal table below the cards shows each deal on its own row. ### Deal statuses Seven status filters sit on the first filter row. Each deal has one of these statuses. * **Draft:** The deal has been created and is awaiting your submission. * **Submitted:** The deal has been submitted and is under review by Allocations. * **Onboarding:** The deal is being set up, which is when most of Setup is completed. * **Closing:** A close is in progress. * **Close Requested:** A close has been requested and is awaiting review. * **Closed:** The close is complete and the raise is finished. * **Test:** A practice vehicle for trying out the platform, kept separate from your live deals. > Filter out Test vehicles when you are reviewing your live portfolio, and exclude them from any screenshot shared with investors. ### Narrowing the table 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. ### Reading the deal table The table has nine columns. Select the arrows beside any column heading to sort the table. * **Deal:** The name of the vehicle, shown beside its avatar. * **Status:** The deal's current status, from Draft to Closed. * **Type:** Whether the vehicle is an SPV or a Fund. * **Raise Progress:** A progress bar, with the percentage and goal written out below it. * **Management Fee:** The management fee percentage for the deal. * **Carry:** The carried interest percentage for the deal. * **Total Signed:** The total amount investors have signed for. * **Total Wired:** The total amount that has arrived in the account. * **Investors:** The number of investors in the deal. ### Exporting the table Export downloads the table as filtered, so set your filters before exporting. --- # 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/fund-manager.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.