> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/donor-support/getting-started/what-is-a-donor-account-or-donorid.md).

# What Is a Donor Account or DonorID?

A Donor Account (DonorID) is your free personal dashboard for managing giving history and settings in one place.

A Donor Account (also called a DonorID) is your personal dashboard for managing your giving in one place. It is a free Anedot service.

With a Donor Account, you can:

* Give faster with autofilled contact information and saved payment methods
* View your full donation history
* Download or request copies of donation receipts
* Find contact information for organizations you support
* Manage recurring gifts (including updates and cancellations)
* Store payment methods securely for future gifts

{% hint style="info" %}
You do not need a DonorID to donate through Anedot.

To give as a guest on a specific donation, click **Not you? Logout** at checkout.
{% 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.anedot.com/donor-support/getting-started/what-is-a-donor-account-or-donorid.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.