Email Template - Getting Started
Accessing the dashboard
In the admin panel, navigate to: Admin Panel → Designer → Email Templates.
The dashboard shows all 35 templates in a card grid. Each card displays the template name, description, category, status, version count, and last updated date.
Figure 2. Accessing Email Templates in the Designer panel.Dashboard controls
|
Control |
What it does |
|
Search Bar |
Find templates by name or keyword |
|
Category Filter |
Filter by category (Authentication, Events, Engagement, etc.) |
|
Type Filter |
Filter by template type (System or Custom) |
|
Sort |
Order by recently updated, name, or other criteria |
|
Status Tabs |
Toggle between All, Active, Draft, and Inactive |
|
+ New Template |
Create a new branded version or custom template |
Template statuses
|
Status |
Meaning |
What happens to emails |
|
Active |
Version is live |
Members receive this custom version instead of the system default |
|
Draft |
Version is being worked on |
Not sent to anyone - version is saved and must be save and publish to set to active to replace current active version |
|
Inactive |
No custom version enabled |
System template sends via legacy flow as usual |
How statuses work in practice
|
Scenario |
What happens |
|
New community setup |
All templates are Inactive. System templates handle all emails. You customize a template, test it, and save and publish to make it Active. |
|
Updating a live branded template |
Create V2 as Draft while V1 continues sending. Test V2, then save and publish it as the new Active. |
|
Reverting to system template |
Set the Default template to active. |
Versioning
|
Concept |
Description |
|
Default Version |
Marked with a blue “Default” badge. Sent to members as the default system template via legacy flow. |
|
Draft Version |
Marked with an orange “Draft” badge. Not sent to anyone. |
|
Create Version |
Click “+ Create Version” in the editor sidebar to copy the current version as a new draft. |
|
Delete Version |
Click the trash icon next to any non-default version to remove it. |
|
Note: Always create a new version before making significant changes to your current version. This preserves your working template as a fallback. |