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

# Collaborating in Overleaf

Overleaf allows multiple authors to collaborate on manuscripts in real time. This allows coauthors to work on an article at the same time, team members to work on group projects together, reviewers to provide immediate feedback, and students to interact with instructors within their shared documents.

Overleaf provides various collaboration features, including project sharing, track changes, commenting, and collaborator chat.

{% content-ref url="/pages/1dKw6Xecary3htw3O397" %}
[Sharing a project](/collaborating/sharing-a-project.md)
{% endcontent-ref %}

{% content-ref url="/pages/zx7YL5eACxdzP31jXelH" %}
[Track changes](/collaborating/track-changes.md)
{% endcontent-ref %}

{% content-ref url="/pages/PlBTl6Lzf2KuM8dkH8QE" %}
[Commenting](/collaborating/commenting.md)
{% endcontent-ref %}

The technology that powers the simultaneous editing in Overleaf is called [Operational Transformation](https://en.wikipedia.org/wiki/Operational_transformation) or OT for short. Your edits on Overleaf are sent back to the server every few seconds and saved. If two or more people edit the file at the same time, the server is able to "rebase" each change on top of the other changes, so that all of the clients end up at the same version. To notify clients of changes made by other clients, we use [WebSocket](https://en.wikipedia.org/wiki/WebSocket), a technology that allows servers to push updates to connected clients.


---

# 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://docs.overleaf.com/collaborating/collaborating-in-overleaf.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.