--- title: "Understanding Mentions, Replies & Reactions Notifications" slug: "understanding-mentions-replies-reactions-notifications" updated: 2026-07-29T09:58:20Z published: 2026-07-29T09:58:20Z canonical: "documentation.encodify.com/understanding-mentions-replies-reactions-notifications" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.encodify.com/llms.txt > Use this file to discover all available pages before exploring further. # Understanding Mentions, Replies & Reactions Notifications ## Notification Types & Triggers --- This article explains how and when **in-app notifications** are triggered for both **item comments** and **proofing comments**, and how they are delivered across various channels such as **Email**, **Application**, **Slack**, and **MS Teams**. > [!WARNING] > **Note:** While the examples in this article refer to *proofing comments*, the same notification logic applies to *item comments* unless explicitly stated otherwise. | **Notification Type** | **Triggered When...** | **Sent To** | **Channels** | | --- | --- | --- | --- | | Add New Proofing Comment | A new comment is added | Contact specified via user field or code | Email, Application, Slack, MS Teams | | Update Proofing Comment | An existing comment is edited | Contact specified via user field or code | Email, Application, Slack, MS Teams | | Mention | A user is mentioned in a comment or reply | The mentioned user | Email, Application, Slack, MS Teams | | Reply to Comment | A reply is added to a comment *(Not triggered if the reply author is also the comment author)* | Author of the original comment | Email, Application, Slack, MS Teams | | Reaction to Comment | A user reacts to a comment | Author of the original comment | Email, Application, Slack, MS Teams | | Change Proof Comment Status: Resolved | A comment is marked as resolved | Author of the original comment | Email, Application, Slack, MS Teams | | Change Proof Comment Status: Unresolved | A comment is marked as unresolved | Author of the original comment | Email, Application, Slack, MS Teams | > [!WARNING] > 💡 **Note:** The "Application" channel does not require configuration. Notifications will appear automatically in the in-app panel. > [!NOTE] > 💡 **Looking to mention a whole team?** > > Check out our guide on [Team Mentions and Notifications](/v1/docs/team-mentions-and-notifications) for details on how to loop in entire groups at once. ## Example Workflow: How Notifications Are Triggered --- The example below outlines a series of interactions during a proofing session and shows which notifications are triggered, who receives them, and how. | **Action** | **Notification Type** | **Sent To** | **Channels** | | --- | --- | --- | --- | | *David* adds a new proofing comment (Comment 1) | Add New Proofing Comment | Assigned contact | Email, Application, Slack, MS Teams | | *David* edits Comment 1 | Update Proofing Comment | Assigned contact | Email, Application, Slack, MS Teams | | *David* adds a second comment (Comment 2), mentioning *Mykola* | Add New Proofing Comment | Assigned contact | Email, Application, Slack, MS Teams | | Mention | Mentioned user Mykola | Email, Application, Slack, MS Teams | | *David* edits Comment 2, still mentioning *Mykola* and now also *Anna* | Update Proofing Comment | Assigned contact | Email, Application, Slack, MS Teams | | Mention | Mentioned user *Anna* | Email, Application, Slack, MS Teams | | *Anna* replies to Comment 2 | Reply to Comment | The original comment author, *David* | Email, Application, Slack, MS Teams | | *Anna* edits her reply | Update Proofing Comment | Assigned contact | Email, Application, Slack, MS Teams | | *Mykola* replies to Comment 2, mentioning *David* and *Anna* | Reply to Comment | The original comment author, *David* | Email, Application, Slack, MS Teams | | Mention | Mentioned user *David* | Email, Application, Slack, MS Teams | | Mention | Mentioned user *Anna* | Email, Application, Slack, MS Teams | | *David* replies to Comment 2, mentioning *Mykola* and *Anna* | Mention | Mentioned user *Mykola* | Email, Application, Slack, MS Teams | | Mention | Mentioned user *Anna* | Email, Application, Slack, MS Teams | | *Mykola* reacts to *David’s* reply | Reaction to Comment | The original comment author, *David* | Email, Application, Slack, MS Teams | | *Anna* marks Comment 1 as *Resolved* | Change Proof Comment Status: Resolved | The original comment author, *David* | Email, Application, Slack, MS Teams | | *Anna* marks Comment 1 as Unresolved | Change Proof Comment Status: Unresolved | The original comment author, *David* | Email, Application, Slack, MS Teams | ## Guest Users and Notifications --- - Internal users can mention existing guest users in proofing comments and replies, as long as they belong to the same user group. - Guest users can mention internal users in proofing comments and replies as long as they belong to the same user group. - Guest users cannot mention other guest users. - Internal users cannot mention guest users from different user groups. - Guest users can receive email notifications when they are mentioned by internal users. - Internal users can receive in-app and email notifications when they are mentioned by guest users. **Note:** It is currently not possible to configure **separate notification rules for mentions** for **internal** and **guest** user groups. As a result, notifications sent to guest users are the same as those sent to internal users. Read this article on [how to configure Guest users to User Groups](/v1/docs/configuring-the-guest-users-app#prerequisites) for more details. ## Summary --- - Notifications are triggered for **new comments**, **edits**, **mentions**, **replies**, **reactions**, and **status changes** - Mentions and reactions always notify the relevant users, even if they’re not the author - Authors will **not** receive a notification for replying to their own comment - All configured channels are supported: **Email**, **Application**, **Slack**, and **MS Teams** - Mentions between **internal** and **guest** users are only allowed when assigned to the **same user group**