Email Templates — User & Admin Guide

This series explains how an administrator or advanced end user creates, edits, tests, and publishes email templates in Email Studio, and how workflow placeholders are named and resolved.

Who this is for

• Administrators / system administrators who maintain the email library, mailer settings, and workflow notifications.
• Advanced end users who are allowed to design templates but may not be allowed to publish or send test emails.

No programming knowledge is required. Technical details are included only where they explain what the screen will accept or reject.

What Email Studio does

Email Studio is the email template library and designer inside Enezaframework. It lets you:

• Create reusable email templates with a stable code, such as INVOICE_APPROVAL_REQUEST.
• Design the subject, HTML body, and plain-text fallback.
• Declare placeholders such as {{ recipient_name }} and {{ workflow.approvers }}.
• Load a workflow template as a data source, so the designer can suggest real workflow fields.
• Preview the rendered email against sample data.
• Send a test email to one or more addresses.
• Save drafts, publish versions, restore older versions, clone templates, and deactivate templates.
• Review the delivery log for queued, sent, and failed emails.

flowchart LR
    A[Create draft] --> B[Design content]
    B --> C[Declare placeholders]
    C --> D[Choose data source]
    D --> E[Preview & validate]
    E --> F[Test send]
    F --> G[Publish]
    G --> H[Active template sends email]
    G --> I[New draft version created]
    I --> B

Documentation map

Suggested reading paths

Creating your first template 1. Creating and Publishing an Email Template 2. Placeholder Reference

Building a workflow notification 1. Creating and Publishing an Email Template — choose the workflow data source. 2. Placeholder Reference — pick workflow.* values such as approvers and links. 3. Assign the template code in the workflow designer or step settings.

Reviewing a failed email 1. Creating and Publishing an Email Template — see Delivery log and Troubleshooting.

Related guides

• Workflow — Developer Index
• Framework Documentation Index

A note on testing

Per project rules, the developer or agent does not run or claim test results. The user is solely responsible for all testing and validation of the output described in these guides.