> 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/cloud-drm/getting-started/pre-start-checklist.md).

# Pre-Start Checklist

**We’re almost there!** <i class="fa-hands-clapping">:hands-clapping:</i>\
After completing all the setup and configuration steps, let’s make sure everything is fully set up before you start working.

Please go through the following checklist to confirm that everything is ready.

## <mark style="color:$primary;">**Checklist:**</mark>

{% stepper %}
{% step %}

### Branding

Is your branding uploaded and ready?

Make sure all elements of your branding are properly uploaded. \[See [instructions ](/cloud-drm/getting-started/setup-and-configuration/branding.md)here.]
{% endstep %}

{% step %}

### Settings

Are your preset donation amounts set? How about your automatic SMS messages?

Not sure? \[Check [here ](/cloud-drm/getting-started/setup-and-configuration/settings.md)for more information.]
{% endstep %}

{% step %}

### Advanced Fields&#x20;

Have you added all your important custom fields and tags?&#x20;

Make sure these are set up so you can add your contacts properly.  \[See [instructions ](/cloud-drm/getting-started/setup-and-configuration/advanced-fields.md)here.]
{% endstep %}

{% step %}

### Donors

Let’s bring all your [donors ](#user-content-fn-1)[^1]onboard!&#x20;

[Import ](/cloud-drm/getting-started/pre-start-checklist/import-donors.md)existing donors in bulk. You can also add your donors one at a time through the [Quick Actions](/cloud-drm/getting-started/user-interface.md#section-c-quick-actions) section.
{% endstep %}

{% step %}

### Campaigns

Enter all the [campaigns ](#user-content-fn-2)[^2]you’re currently working on or plan to launch.&#x20;

[Import ](/cloud-drm/getting-started/pre-start-checklist/import-campaigns.md)existing campaigns in bulk. You can also add your campaigns one at a time through the [Quick Actions](/cloud-drm/getting-started/user-interface.md#section-c-quick-actions) section.
{% endstep %}

{% step %}

### Collectors

If you already have [collectors ](#user-content-fn-3)[^3]working, make sure to add them to the system.&#x20;

&#x20;\[See [instructions ](/cloud-drm/getting-started/pre-start-checklist/add-collectors.md)here.]
{% endstep %}
{% endstepper %}

<mark style="color:$primary;">**And you're good to go! Hatzlacha!!**</mark>&#x20;

[^1]: Individuals who have donated or are committed to donating money in the future.

[^2]: The cause and purpose of the donation. Every donation is directed towards a specific cause AKA campaign.

[^3]: AKA fundraisers. Individuals that actually collect the money and donations.


---

# 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/cloud-drm/getting-started/pre-start-checklist.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.