Template Manager

Overview

The Mythradon Template Manager allows you to manage the system-generated email and notification templates used throughout the platform. These templates help automate communication for common events such as assignments, invitations, reminders, and system alerts.

Below is a list of available templates and their purpose:

Template	Description
2FA Code	Sent to users containing their Two-Factor Authentication (2FA) code.
Access Info	Sent to new users, typically containing login credentials and initial access details.
Access Info for Portals	Sent to new Portal Users with login credentials and portal access information.
Assignment :: Case	Notifies a user they've been assigned as the owner of a Case.
Assignment :: Lead	Notifies a user they've been assigned as the owner of a Lead.
Assignment :: Opportunity	Notifies a user they've been assigned as the owner of an Opportunity.
Assignment :: Task	Notifies a user they've been assigned as the owner of a Task.
Cancellation :: Call	Notifies a user that a call they are participating in has been cancelled.
Cancellation :: Meeting	Notifies a user that a meeting they are participating in has been cancelled.
Invitation :: Call	Sent when inviting a user to join a scheduled Call.
Invitation :: Meeting	Sent when inviting a user to join a scheduled Meeting.
Mention	Notifies a user that they've been @mentioned in a Stream Post.
Note about Post	Sent when a Stream Post is made on a record the user is following or related to.
Note about Post (no Parent)	Sent when a Stream Post is created that does not relate to a parent record.
Note about Received Email	Notifies users when a group email is received and recorded as a note.
Note about Status Update	Sent when the status of a record changes, notifying users who follow or own the record.
Password Change Link	Sent in response to a forgot password request, allowing the user to reset their password.
Reminder :: Call	Reminder email sent to notify a user of an upcoming Call.
Reminder :: Meeting	Reminder email sent to notify a user of an upcoming Meeting.
Reminder :: Task	Reminder email sent to notify a user of a Task due soon or requiring attention.

To modify a standard template:

• Select Administration → Template Manager from the Menu Button
• Click the appropriate template in the list
• Edit the template as required using the Mythradon Rich Text Editor
• Click the Save button when complete.

Reset to Default

You can press the Reset to Default button if you feel that you have made a mistake when editing a template and would like to reset it to the system default.

---

Merge Fields

You can personalise email subjects and body content by inserting merge fields, which dynamically pull values from the current record into the message.

Merge fields use the format {{fieldName}}. For fields that contain multi-line text or rich content, use triple braces {{{fieldName}}} to prevent unwanted HTML encoding when the field is rendered in the email.

Each template has its own set of available merge fields, listed in its documentation. Custom fields are fully supported—just use the internal field name in double curly braces, for example: {{myCustomFieldName}}.

The template editor uses the Mythradon Rich Text Editor. For advanced editing, you can switch to Code View to modify the raw HTML directly.

Note

Merge field names are case sensitive. Ensure you match the field name exactly as defined.

---

2FA Code Email Template

The 2FA Code email template is used to send a user's unique Two-Factor Authentication (2FA) code when signing in to Mythradon.

This email is only sent if:

• Two-Factor Authentication is enabled for the user, and
• The selected 2FA delivery method is Email.

Default Template Example

Available Merge Fields

Merge Field	Description
{{code}}	The user's secure 2FA code required to complete the login process.

Note

Use this template to customise the look and wording of your 2FA emails. Be sure to include the {{ code }} merge field, so the user receives the correct authentication code. Without it, login will not be possible.

---

Access Info

The Access Info email template is used to send newly created users their login credentials for Mythradon.

Note

This email is only sent if Send Email with Access Info to User is enabled during User creation.

This option is only visible once a valid email address has been entered. (Email address hidden in the example image below.)

This template is based on the User entity and supports merge fields to personalise the message.

Default Template Example

Available Merge Fields

Merge Field	Description
{{createdAt}}	Date and time the user record was created.
{{defaultTeamName}}	Name of the user's default team.
{{emailAddress}}	The user's email address.
{{emailAddressIsOptedOut}}	Indicates if the user has opted out of marketing emails.
{{firstName}}	User's first name.
{{gender}}	User's gender.
{{isActive}}	Whether the account is active and available for login.
{{lastName}}	User's last name.
{{middleName}}	User's middle name (not shown by default in the UI, but available as a field).
{{modifiedAt}}	Date and time the user record was last modified.
{{name}}	Full name (combines {{firstName}} and {{lastName}}; does not include {{middleName}}).
{{password}}	The user's initial password. Note: This is only available at the time of creation.
{{phoneNumber}}	The user's primary phone number.
{{phoneNumberIsOptedOut}}	Indicates if the user has opted out of marketing via phone.
{{salutationName}}	The user's salutation (e.g., Mr, Ms, Dr).
{{sendAccessInfo}}	Boolean indicating whether the Access Info email was triggered upon user creation.
{{siteUrl}}	The URL to your {{ app.name }} instance.
{{title}}	The user's job title.
{{userName}}	The username required to log in.

Note

Use this template to tailor the welcome message and provide clear, branded instructions for new users accessing the system.

---

Access Info for Portals

The Access Info for Portals template is used to email login credentials to newly created portal users.

Default Template Example

Available Merge Fields

This template is based on the User entity and supports the following merge fields:

Merge Field	Description
{{createdAt}}	Date and time the user record was created.
{{emailAddress}}	The user's email address.
{{emailAddressIsOptedOut}}	Indicates if the user has opted out of marketing emails.
{{firstName}}	User's first name.
{{gender}}	User's gender.
{{isActive}}	Whether the account is active and available for login.
{{lastName}}	User's last name.
{{middleName}}	User's middle name (available, but not displayed by default in the user interface).
{{modifiedAt}}	Date and time the user record was last modified.
{{name}}	Full name (combines {{firstName}} and {{lastName}}; excludes {{middleName}}).
{{password}}	The user's initial password. Note: This is only available upon initial creation.
{{phoneNumber}}	The user's primary phone number.
{{phoneNumberIsOptedOut}}	Indicates if the user has opted out of marketing via phone.
{{salutationName}}	The user's salutation (e.g., Mr, Ms, Dr).
{{sendAccessInfo}}	Boolean indicating whether the Access Info email was triggered during user creation.
{{siteUrlList}}	A list of Portal URLs the user can access. See below for how to format.
{{title}}	The user's job title.
{{userName}}	The username required to log into any assigned portal.

Note

A single portal user can have access to multiple portals.
Their username and password will remain the same across all assigned portals.

Displaying the Portal URLs

To list all portal URLs the user has access to, use the following syntax:

{{#each siteUrlList}}
{{./this}}
{{/each}}

Here, {{./this}} is used to output each individual URL from the siteUrlList array.

---

Assignment :: Case

The Assignment :: Case template is sent to a User when they are assigned as the owner of a Case.

This template uses the Case entity as the source for its merge fields.

Enable Case Assignement Notifications

Assignment notifications must be enabled on the Case entity for these emails to be triggered upon assignment.

Default Template Example

Available Merge Fields

This template supports the following merge fields:

Merge Field	Description
{{account}}	Name of the Account related to the Case.
{{assignerUserName}}	Username of the user who assigned the Case.
{{contact}}	Name of the Contact related to the Case.
{{createdAt}}	Date and time the Case record was created.
{{createdByName}}	Name of the User who created the Case record.
{{entityType}}	Entity label. Since this is for Cases, the value will be Case.
{{entityTypeLowerFirst}}	Same as {{entityType}} but with the first letter in lowercase.
{{recordUrl}}	URL linking directly to the Case record.
{{modifiedAt}}	Date and time the Case record was last modified.
{{modifiedByName}}	Name of the User who last modified the Case record.
{{name}}	The Case Name field value.
{{number}}	The Case number.
{{priority}}	Priority level of the Case.
{{status}}	Current status of the Case.
{{type}}	Type of the Case.

---

Assignment :: Lead

The Access :: Lead template is used when an email is sent to a user when they are assigned as the owner of a Lead.

This templates uses the Lead entity as the basis of merge fields.

Default Template Example

Available Merge Fields

Merge Field	Description
{{accountName}}	Account Name field value
{{addressCity}}	Address City field value
{{addressCountry}}	Address Country field value
{{addressPostalCode}}	Address Postal Code field value
{{addressState}}	Address State field value
{{addressStreet}}	Address Street field value
{{assignerUserName}}	Username of the user who has assigned the Lead record
{{campaignName}}	Name of the Campaign that is the source of the Lead record
{{convertedAt}}	Date/Time the Lead was converted
{{createdAt}}	Date/Time the Lead record was created
{{createdByName}}	Name of the User that created the Lead record
{{description}}	Description field value
{{doNotCall}}	Do Not Call field value
{{emailAddress}}	Email Address field value
{{emailAddressIsOptedOut}}	Email Address Opt Out field value
{{entityType}}	Label Name of the Entity. Because this is used on the Lead entity the value displayed will be Lead
{{entityTypeLowerFirst}}	Same as the {{entityType}} merge field with the fist letter in lowercase
{{firstName}}	First Name of the Contact from the Lead record
{{industry}}	Industry value from the Lead record
{{lastName}}	Last Name of the Contact from the Lead record
{{middleName}}	Middle Name of the Contact from the Lead record
{{modifiedAt}}	Date/Time the Lead record was last modified
{{modifiedByName}}	The name of the User that last modified the Lead record
{{name}}	Lead Name field value
{{opportunityAmount}}	Opportunity value of the Lead
{{opportunityAmountCurrency}}	Currency code for the Opportunity value of the lead
{{phoneNumber}}	Phone Number field value
{{phoneNumberIsOptedOut}}	Phone Number Is Opted Out field value
{{recordUrl}}	URL to the Lead record
{{salutationName}}	Contact Salutation field value
{{source}}	Source field value
{{status}}	Status field value
{{title}}	Title field value
{{website}}	Website field value

---

Assignment :: Opportunity

The Access :: Opportunity template is used when an email is sent to a user when they are assigned as the owner of an Opportunity.

This templates uses the Opportunity entity as the basis of merge fields.

Default Template Example

Available Merge Fields

Merge Field	Description
{{assignerUserName}}	Username of the user who has assigned the Opportunity record
{{entityType}}	Label Name of the Entity. Because this is used on the Opportunity entity the value displayed will be Opportunity
{{entityTypeLowerFirst}}	Same as the {{entityType}} merge field with the fist letter in lowercase
{{name}}	Opportunity Name

---

Assignment :: Task

The Access :: Task template is used when an email is sent to a user when they are assigned as the owner of a Task.

This templates uses the Task entity as the basis of merge fields.

Default Template Example

Available Merge Fields

Merge Field	Description
{{assignerUserName}}	Name of the User who has assigned the Task record
{{entityType}}	Name of the current entity
{{entityTypeLowerFirst}}	Name of the current entity with the first letter in lower case
{{name}}	Name of the Task record

---

Cancellation :: Call

The Cancellation :: Call template is used when an email is sent to notify a user that a call they are participating in has been cancelled.

This template uses the Call entity as the basis of the merge fields.

Default Template Example

Available Merge Fields

Merge Field	Description
{{assignerUserName}}	Name of the User who has assigned the Task record
{{entityType}}	Name of the current entity
{{entityTypeLowerFirst}}	Name of the current entity with the first letter in lower case
{{name}}	Name of the Task record

---

Cancellation :: Meeting

The Cancellation :: Meeting template is used when an email is sent to notify a user that a meeting they are participating in has been cancelled.

Default Template Example

Available Merge Fields

Merge Field	Description
{{assignerUserName}}	Name of the User who has assigned the Task record
{{entityType}}	Name of the current entity
{{entityTypeLowerFirst}}	Name of the current entity with the first letter in lower case
{{name}}	Name of the Task record

---

Invitation :: Call

The Invitation :: Call template is used to send an email inviting a user to a Call.

This template uses the Call entity as the source for its merge fields.

Default Template Example

Available Merge Fields

Merge Field	Description
{{dateStart}}	Date and time when the Call is scheduled to start.
{{dateStartDate}}	Date portion of the Call's start time.
{{description}}	Description or details about the Call.
{{entityType}}	Name of the current entity (e.g., "Call").
{{entityTypeLowerFirst}}	Same as {{entityType}} but with the first letter lowercase.
{{isAllDay}}	Boolean indicating if the Call lasts all day.
{{isUser}}	Boolean indicating if the recipient is a user.
{{name}}	Name or title of the Call.

---

Invitation :: Meeting

The Invitation :: Meeting template is used to send an email inviting a user to a Meeting.

This template uses the Meeting entity as the source for its merge fields.

Default Template Example

Available Merge Fields

Merge Field	Description
{{createdAt}}	Date and time when the Meeting record was created.
{{createdByName}}	Name of the User who created the Meeting record.
{{dateEnd}}	End date and time of the Meeting (only if not an all-day event).
{{dateEndDate}}	End date of the Meeting (only if it is an all-day event).
{{dateStart}}	Start date and time of the Meeting (only if not an all-day event).
{{dateStartDate}}	Start date of the Meeting (only if it is an all-day event).
{{description}}	Description or details of the Meeting invitation.
{{duration}}	Duration of the Meeting in seconds.
{{entityType}}	Name of the entity (e.g., "Meeting").
{{entityTypeLowerFirst}}	Entity name with the first letter in lowercase (e.g., "meeting").
{{isAllDay}}	Boolean flag indicating if the Meeting is an all-day event (true/false).
{{isUser}}	Boolean flag indicating if the invitee is a User (true/false).
{{modifiedAt}}	Date and time when the Meeting record was last modified.
{{modifiedByName}}	Name of the User who last modified the Meeting record.
{{name}}	Name or title of the Meeting.
{{parentName}}	Name of the related parent record (e.g., Account or Lead associated with the Meeting).
{{status}}	Current status of the Meeting.

---

Mention

The Mention template is used when an email is sent to a user when they are mentioned in a Stream.

Default Template Example

Available Merge Fields

Merge Field	Description
{{userName}}	Username of the person who mentioned the User the email will be sent to
{{parentName}}	The value of the Name field on the parent record that the Stream is related to
{{post}}	The value of the Stream Post

---

Note about Post

The Note about Post template is used to send an email notification when a new Stream Post is made. This ensures relevant users are kept up to date with activity or discussions related to a particular record.

Stream Posts are often used for internal collaboration, updates, or commentary attached to an entity such as a Case, Lead, Opportunity, or Task. This template delivers the post content and related context directly to the user's inbox.

This template includes the author of the post, the content of the post, and links or references to the associated record.

Default Template Example

Available Merge Fields

The following merge fields are used within the template to insert dynamic values at the time the email is generated:

Merge Field	Description
{{entityType}}	The type of entity the post is related to (e.g. Case, Task, Opportunity).
{{entityTypeLowerFirst}}	Same as {{entityType}}, but with the first letter in lowercase (e.g. case, task).
{{name}}	The name of the entity the post is associated with.
{{parentName}}	The name of the parent record, if the post is linked as a child record.
{{post}}	The content of the Stream Post.
{{userName}}	The username of the person who created the post.

---

Note about Post (no Parent)

The Note about Post (no Parent) template is used to notify users via email when there is new Note created for a Stream Post.

This templates uses the Note entity as the basis of merge fields.

Default Template Example

Available Merge Fields

Merge Field	Description
{{entityType}}	Name of the entity
{{entityTypeLowerFirst}}	Name of the entity with the first letter in uppercase and other letters in lowercase
{{name}}	Value of the entity name field
{{post}}	Value of the Stream Post
{{userName}}	Username of the User that made the post

---

Note about Received Email

The Note about Received Email template is used to notify users when a group email has been received and recorded in the system. This is particularly useful for shared or monitored email inboxes (e.g. support@, info@, or sales@) where multiple users need visibility of incoming correspondence.

The notification provides key details from the received email—such as the sender, subject, and message content—and links it to the relevant parent record.

This template is based on the Note entity and uses its merge fields to populate dynamic content.

Default Template Example

Available Merge Fields

The following merge fields are available for use in this template and will be dynamically populated when the email is sent:

Merge Field	Description
{{entityType}}	The type of entity this note is related to (e.g. Email, Note, Case).
{{entityTypeLowerFirst}}	The same as {{entityType}}, but with a lowercase first letter (e.g. email).
{{fromName}}	The name of the sender as specified in the From field of the received email.
{{name}}	The name or subject line of the received email (stored in the Name field).
{{parentName}}	The name of the parent record the email is linked to (e.g. Customer, Lead, Case).
{{post}}	The body content of the received email.
{{subject}}	The subject line of the received email.

---

Note about Status Update

The Note about Status Update email template is used to notify users when the status of a record has changed. This email is typically sent to users who are either assigned as the owner of the record or have chosen to follow it for updates.

This notification helps ensure that stakeholders remain informed about progress or changes without needing to manually check the system. It supports collaboration and transparency across teams by providing timely updates.

Default Template Example

Available Merge Fields

The following merge fields are available in this template to dynamically populate details about the record and the update:

Merge Field	Description
{{entityType}}	The type of entity being updated (e.g. Case, Opportunity, Project).
{{entityTypeLowerFirst}}	The same as {{entityType}}, but with a lowercase first letter (e.g. case).
{{fieldTranslatedLowerCase}}	Translated and lowercased version of the updated field name, useful in multilingual environments.
{{name}}	Name or title of the record (typically from the entity's Name field).
{{userName}}	The name of the user who made the status update.
{{valueTranslated}}	The new, translated value of the updated status or field (e.g. In Progress, Resolved, etc.).

---

Password Change Link

The Password Change Link template is used to send Users a secure link when they need to update or reset their password.

Below is the standard layout of this template:

Default Template Example

Available Merge Fields

The following merge fields can be used in the template to dynamically insert related information:

Merge Field	Description
{{link}}	URL to the change password page.

---

Reminder :: Call

The Reminder :: Call template is used to notify a user that they have an upcoming call to make or attend.

Default Template Example

Available Merge Fields

The following merge fields can be used in the template to dynamically insert call-related information:

Merge Field	Description
{{dateStart}}	The full start date and time of the call (e.g., 2025-05-17 14:00:00).
{{dateStartDate}}	The date portion only of the call start time (e.g., 2025-05-17).
{{entityType}}	The name of the related entity (e.g., Lead, Contact, Opportunity).
{{entityTypeLowerFirst}}	Same as {{entityType}}, but with the first letter in lowercase (e.g., lead, contact).
{{isAllDay}}	Boolean value indicating if the call is scheduled as an all-day event (true or false).
{{isUser}}	Boolean value indicating if the related person is a user (true) or an external contact (false).
{{name}}	The value of the Name field for the associated entity (e.g., the contact or lead name).

---

Reminder :: Meeting

The Reminder :: Meeting email template is used to notify users of upcoming meetings or appointments. This template is typically triggered automatically as a reminder before the scheduled start time of a meeting or event.

It is designed to be clear, concise, and informative, ensuring the recipient has all the key details required to attend or prepare for the meeting.

Default Template Example

Available Merge Fields

The following merge fields can be used in the template to dynamically insert meeting-related information:

Merge Field	Description
{{dateStart}}	Full date and time of the meeting (e.g. Tuesday, 21 May 2025 at 3:00 PM).
{{dateStartDate}}	Date portion only of the meeting start time (e.g. 21 May 2025).
{{entityType}}	The type of entity associated with the meeting (e.g. Appointment, Call, Consultation).
{{entityTypeLowerFirst}}	Same as {{entityType}}, but with the first letter lowercase (e.g. appointment).
{{isAllDay}}	Boolean value indicating if the meeting is an all-day event (true or false).
{{name}}	Name of the meeting or subject line (typically the value of the entity's Name field).

---

Reminder :: Task

The Reminder :: Task email template is used to notify users of upcoming or due tasks. This template is typically triggered automatically when a task is nearing its due date or time, helping users stay on track with their responsibilities and deadlines.

It is designed to present key task information clearly, prompting the recipient to take action, update progress, or mark the task as complete.

Default Template Example

Available Merge Fields

The following merge fields can be used in the template to dynamically insert task-related information:

Merge Field	Description
{{dateEnd}}	Due date and time of the task (e.g. Friday, 23 May 2025 at 5:00 PM).
{{entityType}}	The type of entity the task is related to (e.g. Task, Follow-up, Action Item).
{{entityTypeLowerFirst}}	The same as {{entityType}}, but with a lowercase first letter (e.g. task).
{{fieldTranslatedLowerCase}}	A translated, lowercase label for the field being referenced (used in multi-language systems).
{{name}}	The title or subject of the task (typically from the Name field of the task entity).

---

See also

• Mythradon Bookshelf Home

• Mythradon Basics

• Mythradon Marketing
• Mythradon Sales
• Mythradon Service
• Mythradon System Administration
• Mythradon Tools

---