> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/masters/main-master-module/privileges/email-template-editor.md).

# Email Template Editor

The **Email Template Editor** is a configurable tool used to create, modify, and manage email templates for system-generated communications. It allows users to design email content, format the email layout, and map dynamic data fields to ensure professional, consistent, and automated email notifications.

## Steps to Configure Email Templates

Step 1: Go to the main menu in the application and click on **Settings**.

1. Select **Privileges,** then click on **Email Template Editor**.

The Email Template Editor screen will open.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-b260c7342d0bc58361af9fa9f0ab2045193abe6c%2Fa5.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 2: Click the **Add** button.

1. Select the required details:
   * **Module**
   * **Template Type**
   * **Template Name**
2. Enter the **Subject** for the email template.

* These details define the purpose and category of the email template.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-1df7659eded2c6704bf69b15c4faae50a485a1a7%2Fa5.1.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 3: In the text editor section, enter the email content as per your requirement.

* Ensure the content is clear, professional, and properly formatted.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-908dad7da9cff12844e8ba89f3abc1695fe61237%2Fa5%2C2.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 4: Select the required formatting tools and editor options available in the toolbar.

* These tools help create a well-structured and professional email template.

<figure><img src="https://4060887901-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2ktZUs9CJyincVDXEmrM%2Fuploads%2Fgit-blob-a0f6702723383511e87f63a67867130688d26a7f%2Fa5.3.png?alt=media" alt=""><figcaption></figcaption></figure>

Step 5: Enter the **From Email Address** and **To Email Address**.

* Ensure that the email addresses are entered correctly for successful email communication.

Step 6: After completing all configurations, click the **Save** button.

1. The system will save the email template successfully.

* The saved template can now be used for automated system-generated emails.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.rbsgo.com/masters/main-master-module/privileges/email-template-editor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
