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

# Offerings

Offerings lists the deals you have been invited into. Open it to review the terms and closing date before you commit.

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

1. **PORTFOLIO** Shows that this screen belongs to the Portfolio workspace, where you act as an investor.
2. **Open Offerings** Counts the offerings that are still open for you to commit to.
3. **Search** Finds an offering by typing the deal's name.
4. **Refresh** Reloads the table so it reflects the latest offerings.
5. **Column headers** Sort the table by any of its four columns when selected.
6. **Unit Price** Shows the price per unit you are offered, with the share class below it.
7. **Closing Date** Shows the date the offering closes to new commitments.

## Offerings and investments

Once you commit to an offering, it moves to **Investments**.

## Share class

{% hint style="warning" %}
**Read the share class before you commit.** Classes in the same vehicle can have different fees, carried interest, and liquidation preference, and the deal's documents set out the terms.
{% endhint %}

## Closing date

Allow time for signing before the closing date.

{% hint style="info" %}
Your identity, accreditation, and KYC (Know Your Customer) checks must clear before a commitment completes, so finish your identity early. Identities are described in **Identities**.
{% endhint %}


---

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