Instance email notifications

Email notifications are the messages your instance sends on its own. Examples are a reply to a form, an order confirmation, or an alert to your team. This section explains how they behave on each kind of instance and how to change the layout they use.

In this section

• Email notifications introductionHow staging and production instances treat outbound email.
• Email templatesThe ready-made email layouts and how to change them.

How an email is built

Each email is a template with a recipient, a sender, a subject and a body, and usually a layout for the header and footer. The CRM module ships two layouts that other modules use for their mail: external_email_layout for customers and internal_email_layout for your team. They take your logo and details from CMS globals, so changing the email logo there changes it in every email.

Example: the emails on an instance

{
  admin_email_notifications(per_page: 3) {
    total_entries
    results { name }
  }
}

{
  "data": {
    "admin_email_notifications": {
      "total_entries": 4,
      "results": [
        { "name": "modules/ins_forms/workflow_documentation_suggest_changes" },
        { "name": "modules/website/contact_us_email" },
        { "name": "modules/website/subscribe_email" }
      ]
    }
  }
}

This ran read-only on the docs.insites.io instance on 1 November 2026.

Common mistakes

• Testing on a staging instance and wondering why nothing arrives. Read the introduction page first.
• Editing each module email to change the logo. Change the email logo in globals instead.
• Sending email during a page request. Send it from a background job, so the page stays fast.

To write your own email templates, see CMS emails.