> For the complete documentation index, see [llms.txt](https://knowledgebase.qommentary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.qommentary.com/qommentary-admin-console/settings/email-notifications.md).

# Email Notifications

Qommentary built-in notification system enables users to stay connected and always in the loop.

{% hint style="info" %}
To configure your SMTP server settings, please refer to [Setup > SMTP Server](broken://pages/-M4vfkfGUzuS67r7_WLY) section
{% endhint %}

Email notifications are defined at a global level and can be customized with your organization's branded HTML templates.

![](/files/-MKXgL6rloSVcNezA-wy)

### Updating email templates

1\. Click on the **Edit** button

2\. Update template HTML on rich text editor

![](/files/-MKXh18QFrQqRPZBBVPu)

{% hint style="info" %}
To restore a template back to it's original default state, simply click on the **Use Default** button
{% endhint %}

3\. Click on **Save** button

### Template placeholder tags

Email templates contain placeholder tags which are replaced with relevant information when email notifications are sent.

For a full list of supported placeholder tags, please refer to below table:

#### Supported tags

| Tag name                    | Description                                  |
| --------------------------- | -------------------------------------------- |
| **\[UserFullName]**         | Name of notification recipient               |
| **\[AdminUserDisplayName]** | User who cancelled the workflow              |
| **\[ReviewerDisplayName]**  | Name of commentary reviewer                  |
| **\[Commentator]**          | Name of user who added the comment           |
| **\[Sender]**               | Name of user who added the comment           |
| **\[Link]**                 | URL of application shared                    |
| **\[Message]**              | Custom messaged sent by sender               |
| **\[StepNumber]**           | Current workflow step number                 |
| **\[SubmitterComments]**    | Custom messaged sent by commentary submitter |
| **\[ApprovalWorkflowName]** | Workflow name                                |
| **\[ReviewerComments]**     | Custom message sent by reviewer              |

#### Tag usage

| Template name         | Supported tags                                                                |
| --------------------- | ----------------------------------------------------------------------------- |
| Comment Added         | `[UserFullName] [Commentator] [Link]`                                         |
| Commentary Mention    | `[UserFullName] [Sender] [Link]`                                              |
| Commentary Share      | `[UserFullName] [Sender] [Message] [Link]`                                    |
| Commentary Watch      | `[UserFullName] [Link]`                                                       |
| Workflow Review       | `[UserFullName] [StepNumber] [SubmitterComments] [Link]`                      |
| Workflow Cancellation | `[UserFullName] [AdminUserDisplayName] [ApprovalWorkflowName]`                |
| Workflow Approved     | `[UserFullName] [StepNumber] [ReviewerDisplayName] [ReviewerComments] [Link]` |
| Workflow Rejected     | `[UserFullName] [StepNumber] [ReviewerDisplayName] [ReviewerComments] [Link]` |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledgebase.qommentary.com/qommentary-admin-console/settings/email-notifications.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.