> 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-other-erp-systems-and-basic-invoice-customers.md). # Edit recipients of notifications in Other ERP Systems (and Basic Invoice customers) This page describes how to edit email recipients for Monitoring Errors and Message Errors for Basic Invoice Customers and for customers using other ERP systems as Bison and Fortnox. * Log in to the Golden EDI web portal: (If you don't have a login you need to request one from our support) * Go to the Connection page by clicking on this meny alternative:

Connection settings meny alternative

* Edit either monitoring report settings by clicking in the bell icon for your company or message report settings by clicking on the bell icon for the connection: {% hint style="info" %} Monitor report settings is not available for Basic Invoice Customers (Using Business Central) {% endhint %}

The connection settings page

Dialog for editing the monitor report settings for a company

Dialog for editing message report settings for a connection

--- # 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-other-erp-systems-and-basic-invoice-customers.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.