The current implementation on Email Templates vs rules makes it difficult to manage a multilanguage scenario. For N templates representing the same notification in different languages, it's needed to generate 1 rule for each language in order to respond the Requester in an appropiate way on their language. In our case, with an international sctructure of different departments abroad, it's implying an enormous collection of rules than, in essence doing exactly the same thing but in different languages.

I think would be very useful to develop i18n characteristic on email templates vs rules, as explained:

• 1:N relationship on "1 template target topic" : "N language implementations".
• Related views grouped by "Target topics".
• If so, just 1 rule will be needed to manage multilanguage scope about an specific trigger. I mean, when I create rule, Atera will implicitly manage "reaction to" multilanguage scenario, always based on the language of Requester on their profile. An example: For an specific Rule "X", when Atera notifies to the Requester (or Technician), it will evaluate the language on his profile, and will make use of templates for this language.