> For the complete documentation index, see [llms.txt](https://videos.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://videos.inforiver.com/writeback-matrix/features/collaborative-commenting.md).

# Collaborative commenting

In this video learn how you can leverage Inforiver's Collaborate feature for the following

(a) Cell-level collaboration with multiple stakeholders

(b) Assigning comments as tasks and tracking closure status

(c) Instant email notifications when someone responds, tags a user or assigns a task

(d) Filter-enabled comment logs to show comments relevant to specific users

(e) Public commenting which allows login using social media accounts

{% embed url="<https://lumel.wistia.com/medias/ga0gfyfeo9>" %}

> ## **Related resources**
>
> #### Feature highlights
>
> [Commenting & collaboration in Power BI](https://inforiver.com/collaborate-powerbi/)
>
> #### User guide
>
> [Commenting and collaboration](https://docs.inforiver.com/working-with-inforiver/8.-commenting-and-collaboration)
>
> #### Blog
>
> [Data-driven comments & conversations in Power BI](https://inforiver.com/blog/general/data-driven-comments-conversations-power-bi/)
>
> [10 key considerations for a commentary solution in Power BI](https://inforiver.com/blog/general/10-key-considerations-for-a-commentary-solution-in-power-bi/)


---

# 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://videos.inforiver.com/writeback-matrix/features/collaborative-commenting.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.