> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/collaboration-and-automation/comments-and-mentions.md).

# Comments and Mentions

Collaborate in context and pull teammates in with @mentions.

### Overview

Comments keep discussion attached to the work item.

@mentions create a high-signal notification to a specific Teammate.

### Key Concepts

* **Comment**: message attached to an item
* **@mention**: notification to a Teammate
* **Permalink**: stable link to an item or comment
* **Follower / watcher**: subscription to item updates (when enabled)

### How It’s Used

Use comments for decisions, status updates, questions, and approvals.

Use external messaging tools only for transient coordination.

Summarize outcomes back into the item record for traceability.

### Benefits

* Clear decision trail inside the work item
* Faster reviews through in-context discussion
* Reduced context loss during handoffs

### Setup Steps

{% stepper %}
{% step %}

### Add a comment

{% hint style="info" %}
Screenshot placeholder: item detail panel with the comment box highlighted.
{% endhint %}

1. Open the task, requirement, or test case.
2. Locate the comment box in the detail panel.
3. Enter the message.
4. Select **Comment** (or submit with Enter).
   {% endstep %}

{% step %}

### Mention a Teammate

1. Type `@` in the comment field.
2. Select a Teammate from the list.
3. Add the expected action and timing.

{% hint style="info" %}
GIF placeholder: type `@` → select a Teammate → post the comment.
{% endhint %}
{% endstep %}

{% step %}

### Edit or delete a comment

1. Open the comment menu (⋮).
2. Select **Edit** or **Delete**.
3. Confirm the change.

Edits and deletions may be limited by role and policy.
{% endstep %}
{% endstepper %}

### Best Practices

* Keep one decision per comment when possible.
* Use a consistent pattern, such as `Decision:` and `Approved by:`.
* Use @mentions for action-required requests only.
* Link related items instead of copying long text.

### Summary

Related:

* [Notification Settings](/collaboration-and-automation/notification-settings.md)
* [Following and Watching Items](/collaboration-and-automation/following-and-watching-items.md)
* [Comments and History](/collaboration-and-automation/comments-and-history.md)
* [Activity Tracking](/collaboration-and-automation/activity-tracking.md)


---

# 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://help.transform.ai/collaboration-and-automation/comments-and-mentions.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.