The wording of the emails the system sends by itself: order confirmations, booking reminders, sign-in codes, invitations, support replies and the like.
Each language is its own version
A template has a separate version per language: English, Farsi, Arabic, French, Spanish and German. Editing one never touches another. English and Farsi start with shipped wording; Arabic, French, Spanish and German start empty, so you write them from scratch.
Which language is used when it sends
The language you are editing on this page has no effect on sending. When the email goes out, the sender picks the language: some features use the recipient's own language (bookings use the guest's), and the rest use the site's default language.
What happens when a language has no version
The system tries, in order: your saved version in that language, the shipped wording in that language, your saved English version, the shipped English wording. If nothing exists it uses a plain built-in message (written only in English and Farsi). So an unwritten language does not send a blank email; the recipient reads English.
A saved version sits on top of the shipped one
For each template and language there is the shipped default and at most one saved override. Saving writes the override, which wins. Reset to default deletes the override and the next email uses the shipped wording again. A change applies to the next email sent.
Variables
Each template lists the variables it can use, such as {{code}} or {{siteName}}, as chips beside the editor.
- A variable that is missing or misspelled becomes empty text, not a visible
{{...}}. A typo makes words vanish without any warning. - Nothing enforces the required ones. You can delete
{{code}}from the sign-in-code email and save it; people then receive an email with no code.
The look comes from the system, not from branding
The email frame has fixed colours and a footer. The footer says "Sent from" followed by the site name (from Branding, or the site name in settings), or "Powered by LogaTech" if there is no name. Changing your brand colours does not recolour emails.
Who receives which email
There are about 66 templates. Most go to customers: portal codes and invitations, orders, bookings, support tickets, course access, renewals and trial emails. Some go to staff: the admin-panel invite, new bookings, content awaiting review, bank transfers to confirm. Staff and customer templates sit in the same list, and a few trial and support-credential templates carry passwords, so edit them with care.
Permissions and plan
You need View to open the page and Manage to save or reset. The Admin role has both; the Editor role has neither. Managing templates is a plan feature, so a plan without it can view but not save.