> 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/stock/orders/notifications.md).

# Notifications

## Overview

Stock orders can send two types of emails:

1. **To your event team** when stock orders are submitted
2. **To the creator of the order** (if not a moderator) when you approve or reject an order

## Emails to the event team (on submission)

When a form responsible submits a stock order, Eventication can notify the email addresses you selected in your notification settings.

### Who receives the email?

You can add notification email addresses at:

* the **stock type** level, and/or
* the **stock order configuration** level

If an order matches both, the recipients are combined.

{% hint style="info" %}
Each new order is only emailed once.
{% endhint %}

{% hint style="warning" %}
Orders that are created or edited by moderators, or orders that are already approved/rejected, are not included in the “new submission” notification email.
{% endhint %}

## Emails to the form responsible (decision)

When you approve or reject a stock order, Eventication can email the form responsible with an update.

{% hint style="info" %}
If multiple forms use the same email address, Eventication may group notifications so that the recipient receives fewer emails.
{% endhint %}


---

# 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/stock/orders/notifications.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.