📨 Email Template

This section allows administrators to create, edit, and manage email templates used throughout the system for sending automated or triggered messages such as user registration, password reset, pro

Navigation: Configuration → Email Template

Overview

The Email Template module provides a centralized way to define the content of all system-generated emails.

Each template contains a subject, body, and a set of tokens (placeholders) that are replaced with real data when the email is sent.

Templates rely on the Email Account Module for sending emails — ensuring every message is sent from an authenticated, properly configured email account.

This setup separates the content layer (Email Template) from the delivery layer (Email Account), making the system modular and easier to maintain.

Details / Purpose

The purpose of this module is to enable easy customization and personalization of all system emails without editing code.

Administrators can update email formats, insert branding, or restore them to default with a single click.

This module helps teams:

• Customize communication tone and structure

• Personalize emails using predefined tokens

• Use project- or module-specific email accounts for sending messages

• Ensure consistent and branded messaging across the platform

💡 Example Use Cases:

• User registration or password reset notifications

• Project activity updates

• Task creation, status change, or assignment notifications

• System alerts and automated responses

🔗 Relationship with Email Account Module

Module	Purpose	Dependency
Email Account Module	Defines SMTP configuration, sender email, and authentication details.	Handles sending of the email.
Email Template Module	Defines the message content (subject, body, and tokens).	Provides what is sent via the configured account.

⚙️ Workflow Example:

1. A system event triggers an email (e.g., “Task Created”).

2. The system fetches the relevant Email Template.

3. Tokens in the template are replaced with real data.

4. The email is sent using the linked Email Account (e.g., [email protected]).

📩 The combination of both modules ensures messages are accurate, secure, and visually consistent across all projects.

🧱 Token Support

Token Example	Replaced With
{{UserName}}	Recipient’s full name
{{ProjectName}}	Name of the related project
{{TaskTitle}}	Title of the associated task
{{Email}}	Recipient’s email address
{{AppUrl}}	Base URL of the application
{{SupportEmail}}	The system’s configured support email
{{Date}}	Current date/time at the time of sending

⚠️ Note: Tokens will only work if supported by the corresponding template type.