# Changes to System-Generated Email setup

{% hint style="info" %}
Please note: this change will apply to all clients as part of this Feature Wave. We recommend reviewing it during your 4-week UAT window.
{% endhint %}

As part of the April 2026 Feature Wave, we are changing the way emails which are automatically sent out from Enate work (i.e. system-generated emails). As part of this the ‘Unmonitored Email Address’ setting in the General Settings section of Builder will no longer be used and is being removed.

### What’s Changing?

Enate is removing the Unmonitored Email Address section from General Settings in Builder, meaning that Admin users will no longer set the Unmonitored Email Address for outgoing admin-type emails. This may previously have been something along the lines of ‘[*no-reply@yourcompanyname.com*](mailto:no-reply@yourcompanyname.com)*’.*

With the new approach, admin emails like this which are sent out from the Enate system have a standard unmonitored email address. This new address is:

* **<no-reply@enate.app>**

For private clouds, Enate will work with clients to create domain names.

### **Email Templates Approach**

Additionally, system standard emails (i.e. with email content defined by Enate) will now be used when notifying Enate users for the following admin activities:

* **New Agent User Creation**
* **Forgot Password & SSO Forgot Password**
* **Password Reset Confirmation**
* **Any other Standard System Notifications**

This means that any Email Templates which you may have previously created / modified will no longer be used for these purposes. Such templates will no longer be viewable or editable in Builder

#### Unmonitored email address to be used for Ticket-Rejected Emails

In addition to this new standard unmonitored email address being used for the above admin activity email, it will also now be used for system-generated ‘Ticket-Rejected’ Emails.

Previously this type of email, generated when a ticket was created without a specific category, would have been sent with the same ‘unmonitored’ address that clients could define in Builder. Please note that the client-definable/editable email template content for ticket rejected emails will still be used for this activity.


---

# Agent Instructions: 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:

```
GET https://docs.enate.net/whats-new/april-2026-feature-wave/april-2026-feature-wave/changes-to-system-generated-email-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.