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

# Notifications

Emails and stuff

**Show form description in emails**: Moderators can add descriptions to forms. This setting controls if you want those descriptions to be added to the emails.

**Show allowance numbers in emails?**: Do you want to show the allowance numbers in the emails that are sent to the forms?

**Show allowance numbers in emails before approval?**: Same as above, only this controls if it is sent even when the form hasn't been approved yet.

{% hint style="info" %}
An example of allowance numbers:

* Sunday, July 5, 2020: **5** attendees & **1** vehicle allowed.
* Monday, July 6, 2020: **4** attendees & **1** vehicle allowed.
* Tuesday, July 7, 2020: **2** attendees & **2** vehicles allowed.

Or:

You are allotted **2 day(s)** for people and **5 day(s)** for vehicles to enter the event, spread over the allowed days as you see fit.
{% endhint %}

**Custom subject for notify and reminder-email**: The subject you want the emails to have when we notify a new form (moderator created) or when a reminder email is sent to the form.

**Custom message for notify-email**: The body of the email when we notify a new form (moderator created).

{% hint style="success" %}
This text area supports [formatting](/event/misc/text-formatting.md) and [variables](/event/misc/variables.md).
{% endhint %}

**Reminder emails configuration**: Configure if reminder emails should be sent. These emails are sent automatically within the last 3 days that the form is still editable.

Options:

* **Always**: Always send a reminder email, even if approved, if people are already added, ... We will not send if the form is not editable anymore.
* **If empty**: Only send reminder emails if there are no people or vehicles in the form
* **Never**: Do not send any reminder emails

**Custom message for reminder-email**: Customise the reminder email body.

{% hint style="success" %}
This text area supports [formatting](/event/misc/text-formatting.md) and [variables](/event/misc/variables.md).
{% endhint %}

**Show form edit end date in emails?**: The person that fills the form can see a date until when this form can be edited in their emails. This checkmark allows you to hide this.


---

# 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.eventication.com/event/accreditation/lists/notifications.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.