> 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/planning/settings/members/leaving-notification.md).

# Leaving notification

Set up notifications for member departures here. Monitoring dropouts helps you manage event planning effectively.

### Enabled

If this rule is disabled, it will never trigger.

### Email addresses to notify

Select the [email addresses](/event/general/email-addresses.md) that should receive a notification if a member leaves the event. These are verified company email addresses.

{% hint style="info" %}
The platform is smart enough to only notify an email address once per member that left the event, even if you have set up multiple rules.
{% endhint %}

### Substations

Select the substations for which you want to get notified. If the member did not have a job in one of those substations, the email will not be sent.

### Minimum time in event

Select a minimum time the member had to be part of the event. This allows you to filter out the people who join the event and leave in minutes.

### Also when no jobs?

Do you want the platform to send you an email, even if the member had no jobs?

### Only if double confirmed?

Filter out the people who had not yet double confirmed their membership with the event. This is useful because people who have not yet confirmed, or have rejected their planning might not be of interest for you.

{% hint style="info" %}
Only visible for events that use our [Double confirmation](/event/planning/settings/members/double-confirmation.md) module.
{% endhint %}

### Also if auto removed?

The system does periodic checks to see if members have to be automatically removed from the event. Do you want to get notified if that happens too?

You can set up as many notification rules as you want.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.eventication.com/event/planning/settings/members/leaving-notification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.