Instance · CMS
Emails Introduction
Last updated 1 November 2026
The email templates your site sends, kept in the CMS with recipient, subject, layout and body.
The CMS keeps the emails your site sends: confirmations, notifications and replies to forms. Each email is a template with a recipient, a sender, a subject and a body. Your code or a form sends it, filling in the details for each message.
Where to find emails
In the admin, open CMS and choose Emails. The list shows every email template. The docs.insites.io instance had four on 1 November 2026, including contact_us_email and subscribe_email.
What an email template holds
| Field | Meaning |
|---|---|
| To | The recipient. Can use Liquid, such as the address from a form |
| From | The sender address |
| Subject | The subject line. Can use Liquid |
| Layout | An email layout for the header and footer |
| Reply to, CC, BCC | Optional extra addresses |
| Body | The message, in HTML with Liquid |
Example template
app/emails/order_confirmation.liquid
---
to: '{{ data.email }}'
from: 'Shop <[email protected]>'
subject: 'Order {{ data.order_id }} confirmed'
layout: mailer
---
<h1>Thank you for your order</h1>
<p>Your order {{ data.order_id }} is confirmed.</p>Use a layout so every email shares the same header and footer. Insites modules use their own email layouts for the mail they send.
Common mistakes
- Sending from an address your domain does not allow. Use an address on a domain set up for sending.
- Leaving out
layoutand expecting a header. Without a layout, the body is sent exactly as written. - Sending many emails during a page request. Send them from a background job, so the page stays fast.