> For the complete documentation index, see [llms.txt](https://help.givechariot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.givechariot.com/disbursements/for-grantmakers/set-up-and-manage-programs.md).

# Set Up and Manage Programs

Programs are designed for grantmakers that operate multiple grantmaking services under the same EIN. Programs let you manage those services separately inside one Chariot account.

<figure><img src="broken://files/G9pmOy49TgjsHyP7kEcJ" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="info" %}
Program workflows and program-specific disbursements can be managed through the dashboard or the Chariot API. See <https://docs.givechariot.com/guides/disbursements>
{% endhint %}

### What is separate for each program

Each program can have its own:

* Account balance and ledger
* Display name
* Logo and branding
* Grant letter
* Legal attestation
* Disbursement activity and reporting

Your team can access the programs from one Chariot account, while the receiving nonprofit sees the funds and communications as coming from the selected program.

***

### When to use programs

Programs may be appropriate if your organization:

* Supports multiple grantmaking brands under one EIN
* Provides disbursement infrastructure for other DAF sponsors or foundations
* Needs separate balances for distinct clients, services, or business lines
* Needs recipient-facing branding and legal language to vary by program

You probably do not need programs if all grants use the same balance, brand, grant letter, and attestation.

***

### Create a disbursement from a program

When creating a disbursement, select or specify the program that should fund and send it. Chariot applies that program's balance, recipient-facing identity, grant letter, and attestation.

Always confirm the program before submission.


---

# 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://help.givechariot.com/disbursements/for-grantmakers/set-up-and-manage-programs.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.