> For the complete documentation index, see [llms.txt](https://docs.partner.aboutyou.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.partner.aboutyou.com/user-guide/notifications-settings.md).
# Notifications Settings
You can manage your email notification preferences by navigating to your user profile settings in the top right corner and selecting "Notifications" from the dropdown menu.
### Email Notifications for Orders
\
The notification system allows you to control which order-related emails you receive, helping you stay informed.
#### Available Notification Types
**New Orders**
Receive an aggregated email summary when new orders are created. Orders are consolidated over a time period and sent once per day. (**Default: Off**)
**Open Orders >24h (Business Hours)**
Receive a daily email if you have open orders without shipment messages older than 24 business hours (business hours exclude weekends). This helps you track orders that may need attention or follow-up,. (**Default: On**)
### Default Notification view for any other user
Select or deselect the checkboxes next to each notification type based on your preferences, then click "Save" to apply the changes.
---
# 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.partner.aboutyou.com/user-guide/notifications-settings.md?ask=&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.
