> 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/action-pages/page-builder/communications-consent.md).

# Communications Consent

Ask donors for permission to contact them. Edit the communications consent text and choose whether email consent starts checked on your Action Page.

**Communications consent** adds a checkbox to your form so donors can give permission for future communications. You set it in the Page Builder under **Page > Form**, in the **Communications consent** section. This article covers the consent text and the default setting.

## Set Up Communications Consent

To set up communications consent:

1. Go to **Action Pages > Pages**.
2. Hover over the page you want to edit.
3. Click **⋮ > Edit**.
4. Select **Page > Form**.
5. Under **Communications consent**, edit the **Consent text**.
6. (Optional) Check **Default to opted in (email only)** so the box starts checked for email consent. Donors uncheck it to opt out.
7. Click **Save**.

The consent checkbox and text show on the form the next time donors load the page.

## Related Articles

* [Standard Form Fields](/action-pages/page-builder/standard-form-fields.md)
* [Page Builder Overview](/action-pages/page-builder.md)


---

# 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/action-pages/page-builder/communications-consent.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.