Email Message Templates

Many of the automated emails sent to parents and staff can be customised to meet your language requirements. To find the templates, navigate to Administration → Site Administration → Manage Email Messages.

Click on edit next to the template you wish to edit.

Depending on the template you are editing, you may see one or more of the following sections:

Click on Save Message when done.

Editing the Default Template

Where schools have demanding CI requirements, ADAM allows for the customisation and modification of the default email template.

Kindly note that we do not provide any support for the modification or formatting of email messages. This feature is provided for your use entirely at your risk. In the event that your email template is changed in any way, our only offer of support is to replace this with the default message template.

Navigate to Administration → Site Administration → Manage Email Messages. Click on edit next to the All Email template, listed under the General heading.

Unlike other message templates, this one does not provide a “rich” text editor and, instead, provides the raw HTML that is used to format every message - including the other templates that ADAM lists.

Note carefully the four merge codes. The {body} and {footer} merge codes MUST be included in the template.

Please be aware that while this allows you to enter and CSS and HTML code you wish, not all CSS styling and HTML is honoured by the email client that will show the email to the final recipient. Additionally, there is no standard as to which email clients honour which CSS directives, meaning that to get an email to display consistently across all email viewers is, in short, impossible. A simple Google search on “email css styling” will reveal as much. You are thus advised to keep your styling general and also to test it across as many email clients as possible to ensure that emails are displayed correctly and are legible in their final destinations. ADAM will not attempt to make any suggestions or corrections and will assume that you know what you’re doing!

Alternatively, there are a number of HTML template generators available who will ensure that your emails look as consistent as they can across different email clients. However, these are normally not free and should be used at your own risk.

Finally, if your school employs a graphic designer, they might be able to assist you with the creation of an HTML template.

Using banner images

There are two merge codes for banner images: {bannertop} and {bannerbottom}. These banners should be uploaded in the same place as the school logos.

Be aware that these banners are not automatically resized by ADAM. While the banner images can be resized in the CSS of the email (perhaps with a surrounding div tag with fixed dimensions), again be aware that no all email clients will support such modifications and you are advised to upload appropriately sized images that will display correctly for a large number of users without and styling intervention. Again, we emphasise the need to test your emails on a wide variety of email clients and platforms!

Staff Email Signatures

A number of merge codes are provided to allow ADAM to customise the email signature depending on which staff member is sending the email. It is also possible, using the {staffsignature} directive, to have ADAM use the most recently uploaded image file from the staff member’s document repository as an email signature.

Because ADAM pulls the most recent one, to update it, all you need to do is upload a new one.

To upload signatures in bulk, please look at the Document Repository documentation for instructions.

You will need to ensure that your images are a suitable width, or that your template contains the necessary HTML to ensure that any over-sized images render correctly on narrower screens.

Note that if a staff member does not have a signature, ADAM will not put a “default” signature in its place, and instead, no image will be displayed.