> For the complete documentation index, see [llms.txt](https://docs.unifize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unifize.com/release-notes/january-2026/square-bracket-on-approval-notification.md).

# Square bracket on approval notification

### **Introduction**

This release focuses on improving the reliability and consistency of **approval automation notifications**. The focus is on improving how user and group mentions are handled inside automated messages configured under **Automations on approval**, **Automations on rejection**, and **Automations on cancellation**.

With these improvements, admins can expect notification messages to render accurately, without formatting artefacts, and with better validation of supported characters.

***

### **What this release covers**

This release addresses issues observed when admins configured a “Send a message” automation and tagged a user group whose name included parentheses:

* Messages occasionally displayed random closing square brackets (`]]]]`), even when not present in the original configuration.
* These formatting errors appeared both in the automation builder and in the final delivered message.

Enhancements implemented include:

* Updated formatting logic to ensure tags/mentions are rendered cleanly and consistently.
* Strengthened validation, preventing admins from entering unsupported characters (`[` or `]`) in user and group names.
* More reliable translation between the UI mention format and the server-side format used for notification delivery.

***

### **Before vs After**

| **Scenario**                                                                    | **Before**                                                   | **After**                                                       |
| ------------------------------------------------------------------------------- | ------------------------------------------------------------ | --------------------------------------------------------------- |
| Tagging a group with parentheses in its name inside “Send a message” automation | Random trailing brackets (`]]]]`) appeared in notifications. | Mentions render correctly with no unwanted characters.          |
| Mention formatting between UI and server                                        | Inconsistent formatting caused artefacts in final messages.  | Formatting is now aligned, stable, and error-free.              |
| Entering unsupported characters in user/group names                             | Allowed in certain cases, resulting in broken formatting.    | `[` and `]` are now blocked with an immediate validation error. |
| Notification preview vs actual message                                          | Could differ due to rendering bugs.                          | Both now display the same, accurate output.                     |

***


---

# 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://docs.unifize.com/release-notes/january-2026/square-bracket-on-approval-notification.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.