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

# Portfolio Overview

Portfolio is the workspace for the capital you invest yourself. It covers your offers, positions, payouts, and the identities and accounts you invest through.

## Switching to Portfolio

Select **Portfolio** in the workspace switcher at the top of the sidebar. The sidebar then shows the Portfolio screens.

## The eight screens

* **Investor Dashboard:** Shows your portfolio value and every investment in one table.
* **Investments:** Shows the same positions in a full-screen table.
* **Offerings:** Lists the deals you have been invited into, with the price offered.
* **Identities:** Holds the people and companies you invest through.
* **Taxes:** Holds the K-1s issued to you, with a FAQ on Form 1065.
* **Cash Accounts:** Records the bank accounts and crypto wallets you invest from and receive money into.
* **Brokerage Accounts:** Records the brokerage accounts you have registered for receiving securities.
* **Distributions:** Lists the proceeds paid to you from the deals you hold.

## **Shared screen names**

Four screen names appear in both workspaces, and each opens a different screen depending on the workspace:

* **Taxes:** Funds holds the returns you file for each entity, while Portfolio holds the K-1s you receive.
* **Distributions:** Funds lists the payouts you issue, while Portfolio lists the money paid to you.
* **Identities:** Funds uses the identity filling a deal role, while Portfolio holds the identities you invest through.
* **Dashboard:** Funds leads with assets under management, while Portfolio leads with your portfolio value.


---

# 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/portfolio-overview.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.