Feature Suggestion

As a system admin, I would like to have a warning message when the toggle is clicked on the connector which is enabled. As of today, any user who mistakely clicks on toggle - the conector will go off without any warning and the user is easy to miss that the toggle is off and we also miss the logs on who did the change

We need Enate system emails (password resets, notifications, etc.) to be sent using Enate‑managed email infrastructure, rather than routing through our own email gateways. This will improve reliability, reduce configuration overhead on our side, and ensure system emails are consistently delivered without depending on our internal SMTP/M365 setup.

We need Enate to prevent users from typing any “From” address when sending emails. Instead, users should only be able to select from a predefined, validates list of addresses. This will help us stay secure, prevent misuse of email identities, and ensure compatibility with our M365/Graph policies.

In Enate, the email separator currently displays as a series of multiple dashes (------). This makes long email threads harder to read and looks visually outdated. Please update the email separator to match Outlook’s style — a clean, straight horizontal line — to improve readability and align with modern email UI standards.

As a Work manager user, I want to define a custom sort order for values on bar charts, So that the data is presented in a logical progression rather than a default number of work item based sequence. For example, in the attached screenshot, having priorities from P0 to P5 is helpful rather than based on number of work items.

We have examples of regular and ad hoc incoming emails .. both from internal and external sources where multiple team mailboxes (i.e. Enate connectors) are on the bcc line of the email. When this email comes into Enate a single ticket is created, for one connector which I believe is chosen alphabetically. This is down to how Enate processes the email and its visibility of the mailboxes in the bcc line. However, from a user perspective this is a degrading of service from when they used to operate directly from their mailbox e.g. Outlook and were standing independently. Here they would have received an email each and acted on it. Each team needs their own ticket created. In Enate the team that does not get a ticket have no knowledge of an email having arrived. The team that does get the ticket have no knowledge that other teams should also have had this ticket created for them. If they had, they could create linked tickets for other teams. When two or more mailboxes are on the To of an email it is recognised that they all need this email and a ticket is created for each. Can the email processing logic of bcc be looked at so that the independence of different connectors is recognised in Enate?

Current behaviour: When a client sends an email that creates a work item in Enate, the system automatically sends an acknowledgement email to confirm receipt. However, there is currently no option to automatically send a closing acknowledgement when the ticket has been completed. Expected behaviour: Provide the ability to configure an automatic closing acknowledgement email that is sent to the client when the work item or ticket is resolved. Impact: Sending a closing acknowledgement would help keep clients informed that their request has been completed, reduce follow-up emails requesting status updates, and provide a clear confirmation that the issue has been resolved.

There are several operational scenario where in we will need ability to search inside attachments for specific worlds. These attachments are usually PDF and Excels.

As a Super User of HRP in Poland, I would like to pass on the suggestion of local users that we would like to be able to choose whether we work on dark or light Enate mode. I wonder if such an idea has more supporters.

As a user, we would need an integration for emails going out of Enate to Microsoft Purview. As this is being used globally inside the company - Enate is not able to deliver this currently. Can you please help on generating any such feature integration to send out emails with Microsft Purview enabled