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

# Syndicates

Syndicates lets you raise through a standing group of investors, so a group you have assembled once can be invited to each new deal together.

A syndicate is a named group of investors with its own description, and it stays in place from one deal to the next.

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

1. **Search syndicates** Finds a syndicate by typing any part of its name.
2. **Filter** Opens the filter panel, with the number of conditions applied in brackets.
3. **Toolbar** Lets you refresh the list or create a syndicate.
4. **Column headers** Sort the table by any of its four columns when selected.
5. **Name and description** Show the syndicate's name and the proposition investors are invited to join.
6. **Status** Shows whether the syndicate is published and visible to investors.
7. **Investors** Counts the members who have joined the syndicate.
8. **Row menu** Opens the actions available for that syndicate, such as editing it or inviting members.

### Publishing a syndicate

PUBLISHED means investors can see the syndicate, so review its description and terms before you publish.

### The investor count

The Investors column counts the members of the syndicate. Total Investors on the Dashboard counts investors across all vehicles.

### Filtering

To see every syndicate, check the number on the Filter button and clear any conditions.


---

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