> For the complete documentation index, see [llms.txt](https://help.donary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.donary.com/overview/lists/donors.md).

# Donors

## Overview

<mark style="color:$primary;">**You can access the Donors tab via the Lists category in the left sidebar.**</mark>

The **Donor List** is your comprehensive hub for all donor-related information, where you can easily add, find, and edit details for any donor. Each donor profile includes all essential information needed such as contact details, donation history and more.&#x20;

## Features

There’s a lot to explore in this section! Let’s take it one step at a time and dive into each feature the DRM offers under the Donor tab.

<table data-view="cards"><thead><tr><th align="center"></th></tr></thead><tbody><tr><td align="center"><a href="/overview/lists/donors/donors-list-view.md"><mark style="color:$primary;"><strong>Donor List View</strong></mark></a></td></tr><tr><td align="center"><a href="/overview/lists/donors/add-a-donor.md"><mark style="color:$primary;"><strong>Add A Donor</strong></mark></a></td></tr><tr><td align="center"><a href="/overview/lists/donors/donor-card.md"><mark style="color:$primary;"><strong>Donor Card</strong></mark></a></td></tr></tbody></table>


---

# 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.donary.com/overview/lists/donors.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.