> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/actions/grids/review-content-in-the-grid/collaboration.md).

# Real-time Collaboration

## Collaborate on Content in Grid

AirOps Grid provides powerful real-time collaboration features that enable your team to work together seamlessly on content. These features are available for HTML and Markdown columns, allowing multiple team members to review, comment on, and refine content simultaneously.

> **Note**: Real-time collaboration features are available for Enterprise customers.

### Comments

Add comments directly in your documents, start threads, reply to comments, and edit your own comments, all without leaving the content editor.

#### How to Use Comments

1. **Add a Comment**: Highlight text in your HTML or Markdown content, then click the comment button to add your comment
2. **View Comments**: All comments appear in a sidebar panel on the right side of the editor
3. **Reply to Comments**: Click on an existing comment to view the thread and add your reply
4. **Edit Comments**: Modify your own comments using the edit option
5. **Resolve Comments**: Mark comments as resolved once feedback has been addressed
6. **View Resolved Comments**: Access resolved comments from the comments panel to review past discussions

#### Comment Count in Grid View

See comment activity at a glance with comment counts displayed directly in the Grid. Cells with active comments show a count indicator, making it easy to:

* Identify which content has active discussions
* Prioritize content that needs review attention
* Track feedback across your entire Grid without opening each cell

### Suggestion Mode

Propose edits without changing the original content, similar to Google Docs' "Suggesting" mode. This is perfect for collaborative reviews where you want to suggest improvements without directly applying changes.

#### How to Use Suggestion Mode

1. **Toggle Suggestion Mode**: Open an HTML or Markdown cell and use the mode dropdown in the editor (default is "Edit Mode")
2. **Switch to Suggestion Mode**: Select "Suggestion Mode" from the dropdown
3. **Make Suggestions**: Any edits you make will appear as suggestions rather than direct changes:
   * Deleted text appears with strikethrough formatting
   * Added text appears highlighted in green
4. **Review in Comments Panel**: Each suggestion automatically appears in the comment panel, showing who made the suggestion
5. **Accept or Reject**: Collaborators can accept or reject suggestions with a single click:
   * **Accept**: Merges the suggested change into the document
   * **Reject**: Removes the suggestion without applying the change
   * **Delete**: Removes the suggestion entirely

#### When to Use Suggestion Mode

* Collaborative content reviews where multiple stakeholders need to weigh in
* Editorial workflows where editors suggest changes for writers to approve
* Quality assurance processes where reviewers flag potential improvements

### Version History

Track changes and roll back to previous versions of your content when needed. Accidentally overwrote something or ran a workflow that didn't produce the desired result? You can roll back to any previous version.

#### How to Use Version History

1. **Access Version History**: Open the HTML or Markdown editor and click the arrow icon in the top right corner
2. **View Previous Versions**: Browse through the list of saved versions, each showing:
   * Timestamp of when the version was saved
   * Who made the changes
   * **Lightning bolt icon**: Indicates the version is an output from a workflow run
   * **User icon**: Indicates the version was created by manual user edits
3. **Compare Versions**: Click on older versions to see exactly which edits were made and who made them
4. **Roll Back**: Restore a previous version if needed by selecting it and clicking "Restore"

Version history is automatically maintained as changes are made, ensuring you never lose important content iterations.

### Live Presence

See exactly who's in the document with you in real-time. No more stepping on each other's toes or duplicating work.

#### How Live Presence Works

* **Presence Indicators**: When you open an HTML or Markdown cell, you'll see avatars showing other team members currently in the same cell
* **User Count**: At the bottom of the cell, see how many users are currently editing
* **Real-time Updates**: See when collaborators enter or leave the document
* **Collision Prevention**: Know when someone else is editing to coordinate your work

### Availability

Real-time collaboration features are available for:

* **HTML columns**: Full support for comments, suggestion mode, version history, and live presence
* **Markdown columns**: Full support for comments, suggestion mode, version history, and live presence

### Best Practices for Team Collaboration

1. **Use Suggestion Mode for reviews**: When reviewing others' content, switch to Suggestion Mode to propose changes without overwriting their work
2. **Add context with comments**: Use comments to explain your suggestions or ask questions about specific content
3. **Check live presence**: Before making major edits, check if someone else is currently working on the same content
4. **Leverage version history**: Don't hesitate to experiment. You can always roll back if needed
5. **Resolve comments**: Keep your content clean by resolving comments once they've been addressed


---

# 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.airops.com/actions/grids/review-content-in-the-grid/collaboration.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.
