> 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/collaborating-in-transform.md).

# Collaborating in Transform

Work together using comments, notifications, and activity history.

### Overview

Collaboration is centered on shared context inside the work item.

It keeps decisions, updates, and accountability visible and searchable.

### Key Concepts

* **Comments**: decision and discussion trail attached to an item
* **Notifications**: signals for changes that need attention
* **Activity history**: timestamped record of changes

### How It’s Used

Use comments to record decisions and approvals.

Use notifications to react to assignments, mentions, and due dates.

Use activity history to validate what changed and when.

### Benefits

* Reduced context loss across teams and time
* Cleaner governance through traceable decisions
* Faster onboarding for new delivery teams

### Setup Steps

1. Standardize a comment pattern for decisions, such as `Decision:` and `Approved by:`.
2. Tune notification settings to prioritize mentions and assignments.
3. Use activity history during weekly reviews to validate progress signals.

### Best Practices

* Keep approvals inside the item record, not in external message threads.
* Link related requirements, tasks, tests, and Artifacts instead of copying text.
* Use Save Views to pair collaboration signals with repeatable review lists.

### Summary

* [Communication](/collaboration-and-automation/communication.md)
* [Notifications](/collaboration-and-automation/notifications.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/collaborating-in-transform.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.