> For the complete documentation index, see [llms.txt](https://guide.charityvest.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.charityvest.org/community-funds/community-fund-setup.md).

# Community Fund Setup

Guidance on how to set up Charityvest's newest feature, Community Funds.

Charityvest Community Funds were designed to be a simple and seamless way for community leaders to pool charitable capital via a custom-branded webpage. 

{% hint style="info" %}
**Interested in leading a community fund?** \
Fill out this [request form](https://forms.gle/Xd1Sw8NS5cJrnroZ8) and our team will contact you to begin the process. 🚀
{% endhint %}

## Getting Started

Our team will work with you 1:1 to create your first fund! Here are the steps to bring your fund to life:

* [ ] [**Agree** ](/community-funds/community-fund-setup/community-fund-policies.md)to our Community Fund policies. 
* [ ] [**Set** ](/community-funds/community-fund-setup/community-fund-settings.md)your preferences for privacy, fees, and more.
* [ ] [**Design** ](/community-funds/community-fund-setup/community-fund-design.md)your fund with a name**,** tagline**,** keywords, images, rich text, links, and FAQs.

Here's an in-depth product walkthrough:

{% embed url="<https://www.loom.com/share/d2e6fba9329b4b65bb40ec907969795d>" %}

Once your fund is set up, you can share it as broadly as you'd like, to collect donations and issue grants to charities.


---

# 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://guide.charityvest.org/community-funds/community-fund-setup.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.