> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/golden-edi-support-and-monitoring-documentation/edit-recipients-of-notifications-in-business-central-nav.md).
# Edit recipients of notifications in Business Central / NAV
This page describes how to edit email recipients for Monitoring Errors and Message Errors in Business Central and Microsoft Dynamics NAV.
* Go to **GEDI Profile** by searching for "gedi profile"
Screenshot from BC how to retrieve GEDI profiles
* On the GEDI profile **INTERNAL**, you can change the e-mail address of the recipient(s) who will receive monitoring errors (as well as the monitoring report) in the *E-mail to System Administrator* column.
Screenshot from BC where to edit monitor error receiver
* For message errors (as well as the message report), you change the e-mail address of the recipient(s) who should receive the report in the column *E-mail to GEDI administrator* for the respective GEDI profile / connection
Screenshot from BC where you change recipients of message errors
If you want to enter more than 1 e-mail address for monitoring errors or message errors, you separate the e-mail addresses with semicolons (;)
---
# 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.goldenedi.com/golden-edi-support-and-monitoring-documentation/edit-recipients-of-notifications-in-business-central-nav.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.
