> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/system-management/settings/email-templates.md). # Email templates To convey your company brand, you can [create customized email templates](#create-email-template) with your organization's logo, formatting and boilerplate text. DoControl also provides default options for [formatting templates](#format-email-template). You can use customized email templates as part of a workflow for these actions: * [Approval](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/decide/approval.md) * [Decision](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/decide.md) * [Notify by email ](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/notify.md#notify-by-email) {% hint style="warning" %} You need **Admin** permission to create and edit email templates. {% endhint %} When adding an email **Approval**, **Decision**, or **Notify** **by email** step, you only need to select the predefined email template. All the content and formatting is automatically included in the email, which you can further modify if necessary.

Customize email templates with your company branding and formatting

## Create email template {% hint style="info" %} * If you don't create any customized email templates, the default template is used. * You can create up to 20 email templates. {% endhint %} 1. From the top-right corner in any screen, select **Settings > Workflows > Email templates**. 2. Give your template a name, and type the body text. 3. Define the [formatting options](#format-email-template) for your email template. 4. Click **Save**. Your template appears in the template list on the left. \ When you define a workflow with an Approve or Notify step by email, clicking the **Templates** link will display your email templates. 5. To edit an existing template, select any predefined template from the list. 6. To clear all fields and start a new template, click **Create new template**.

## Format email template DoControl provides [default formatting options](#default-formatting-options) for email templates. {% hint style="success" %} In addition to formatting options, you can insert any HTML tag in an email template. {% endhint %} ### Default formatting options

Icon	Email formatting option	Description
	Bold	Applies bolded font to selected text.
	Italics	Applies italicized font to selected text.
	Strikethrough	Crosses out the selected text.
	Paragraph	Applies paragraph style to selected text.
	Heading 1	Applies first-level heading style to selected text.
	Heading 2	Applies second-level heading style to selected text.
	Code	Applies code style to selected text.
	Code block	Applies code block style to selected text.
	Quote	Applies block quote to selected text.
	Bulleted list	Applies bullets to an unordered list.
	Ordered list	Applies numbering to an ordered list.
	Line break	Splits a long line into two lines.
	Horizontal rule	Inserts a horizontal divider between sections.
	Clear format	Removes all applied formatting.
	Insert image	Uploads an image file. You can modify the zoom level and size of the image as you upload it.
	Undo	Removes previously applied formatting.
	Redo	Re-applies last formatting that was removed.

--- # 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://docs.docontrol.io/docontrol-user-guide/system-management/settings/email-templates.md?ask=&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.