> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/email-templates.md).

# Email Templates

IZ Suite sends emails from templates: notifications, invitations, password resets and a shared footer. Every workspace uses the shared default templates, which stay up to date automatically, until it customizes one. Use this tab to review the templates and edit their HTML.

Open it from **Administration** → **Global Settings** → **Email templates** in the sidebar.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FlwprhLHHnkcWjmO0RVuw%2Fv2-gs-email.png?alt=media&amp;token=838613d8-d702-4435-a5c1-1ff5c0f09297" alt="Email templates list with category, events, source tag and Edit template"><figcaption><p>Email templates</p></figcaption></figure>

{% hint style="warning" %}
You need a role that can view global settings to open this tab, and a role that can edit global settings to change a template. Without it, each template opens read-only with **View template**.
{% endhint %}

## Message Templates

Use **Search templates or events** to find a template by name, title or notification event. The source filter shows **All templates**, **Using default** or **Customized**, and the refresh button reloads the list.

Each template shows:

| Item               | Description                                                                                                                                     |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Name               | The template's name.                                                                                                                            |
| Category and title | For example **Notifications** · **Application removed**, **Account access** · **Reset your password**, or **Shared footer** · **Email footer**. |
| Events             | How many notification events use the template.                                                                                                  |
| Source             | **Using default** or **Customized**.                                                                                                            |
| **Edit template**  | Opens the template editor (**View template** for read-only roles).                                                                              |

## Edit a Template

1. Click **Edit template** on the template.
2. Edit the HTML under **Email HTML**. Keep the variables the message needs.
3. Check the **Preview**.
4. Click **Save workspace template**.

<figure><img src="https://content.gitbook.com/content/9vAxMuDrkUkB4OXlH9CL/blobs/SOmOnPAugUA6w2AS2IHc/.gitbook/assets/gs-email-templates-editor.png" alt="Template editor with the HTML editor, template variables and preview"><figcaption><p>Template editor</p></figcaption></figure>

| Item                   | Description                                                                                                                        |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Email HTML**         | The template's HTML. Variables are written in double braces, for example `{{appStats.appName}}`.                                   |
| **Format HTML**        | Tidies the indentation of the HTML.                                                                                                |
| **Start from default** | Replaces the editor content with the shared default, so you can start over. Saved only when you click **Save workspace template**. |
| **Template variables** | Expand it to list the variables this template can use.                                                                             |
| **Preview**            | Renders the template with example data. No email is sent.                                                                          |

Saving applies the template to this workspace only. Other workspaces keep their own settings.

## Go Back to the Default

A customized template can switch back to the shared default and receive future default updates again.

1. Open the customized template.
2. Click **Use default template**.
3. Confirm with **Use default template**.

{% hint style="danger" %}
This replaces your workspace's customization. The template's email events switch back to the shared default.
{% endhint %}

## Next Steps

* [Organization Subscriptions](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/notifications/organization-subscriptions.md): choose who receives the notification emails.
* [Settings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/settings.md): review the other workspace settings.
* [Global Settings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings.md): the other configuration screens.


---

# 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://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/email-templates.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.
