> For the complete documentation index, see [llms.txt](https://docs.samita.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.samita.io/samita-wholesale-b2b/setting/set-up-notifications.md).
# Set up notifications
Customize the emails sent to you and your customers for payment terms and invoice payments, and configure your mail sender.
The **Notifications** tab in Settings is where you customize the emails the app sends out, and where you configure the mail server those emails go through.
## Steps to manage
{% stepper %}
{% step %}
### Open Notifications settings
From the app, click **Settings**, then click **Notifications**.
{% endstep %}
{% step %}
### Edit a notification template
Under **Payment terms** or **Invoice payments**, click **Merchant notification** or **Customer notification** to edit that email's content.
* **Merchant notification** — the email you (or your team) receive.
* **Customer notification** — the email your customer receives.
{% endstep %}
{% step %}
### Configure your mail sender (optional)
Under **Mail SMTP & API**, you can send these emails from your own email address instead of the app's default sender. See [Set up SMTP](/samita-wholesale-b2b/registration-form/set-up-smtp.md) for the full walkthrough.
{% endstep %}
{% endstepper %}
> ### **Need support?**
>
> If you do encounter any difficulty while proceeding these steps, don’t show any hesitation to contact us promptly via the email address [support@samita.io](https://help.samita.io/support@samita.io)
---
# 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.samita.io/samita-wholesale-b2b/setting/set-up-notifications.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.
