> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/features/emails/email-preferences.md).

# Email preferences

All Perkville users can set their email preferences via their account settings:

1. Click **Settings** in the header menu (if you are in the Perkville dashboard click your name and then **Settings**)
2. Click **Email** in the left-hand menu (under **Account** if you are in the Perkville business dashboard)
3. Check or uncheck the emails you'd like to receive
4. Click **Save**

<figure><img src="https://2181708597-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSiE75SeColbiBVbet0NZ%2Fuploads%2FqEvRd4eccAuo6hkxeb4Q%2FScreenshot%202025-06-27%20at%203.05.30%E2%80%AFPM.png?alt=media&#x26;token=0882c152-3f6d-48f4-8cc7-7d4157fbddcb" alt=""><figcaption><p>Subscribe or unsubscribe from Perkville emails via your account's email settings</p></figcaption></figure>

{% hint style="warning" %}
Updating a customer’s email preferences in one business profile will automatically update these settings across all businesses the customer is connected to. This ensures consistent communication preferences regardless of which business they interact with within Perkville.
{% endhint %}

{% hint style="info" %}
This is also the page where you and your customers can add or remove email addresses to their account
{% endhint %}

If a customer has stopped receiving expected Perkville emails, see [email delivery troubleshooting](https://docs.perkville.com/faqs/managing-emails-and-names/my-customer-says-theyre-not-receiving-email-why.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.perkville.com/features/emails/email-preferences.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.
