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

# Working with Others

Multiple users can have a scenario open at the same time. Agentnoon shows who else is present and lets you coordinate via comments. Give edit access only to active collaborators and use view-only for stakeholders who just need visibility.

## Real-Time Presence

When other users have the same scenario open, their **profile icons** appear at the top of the scenario. Hover over an icon to see the user's name.

<figure><img src="/files/FWj56dmOSz8CdjptoaK6" alt=""><figcaption></figcaption></figure>

Use presence indicators to:

* Know when a colleague is actively reviewing your work
* Coordinate who is working on which section before making changes
* Avoid editing the same positions simultaneously

## Coordinating with Collaborators

Since multiple users can edit a scenario with Edit Access, coordinate to avoid conflicts:

1. Add a comment announcing which section you're working on (e.g., "Working on Engineering — taking until EOD")
2. Check the presence icons before making large structural changes
3. Work in different departments or branches to minimize overlap
4. If two users edit the same position simultaneously, the last save wins — use OpEx Panel to review what happened

## Best Practices

* **Communicate first** — Use comments to announce your focus area before making changes
* **Divide by section** — Work in different departments or functions
* **Review together** — Walk through the final scenario as a team before submitting for approval
* **Limit concurrent editors** — 2–3 people editing at once is manageable; more can cause confusion

:bulb:**Protip —** Use Comments to explain changes and document assumptions. This is especially important for changes that might need justification during approval.

Give edit access only to active collaborators; use view-only for stakeholders who just need visibility

## Related Articles

* [Sharing Scenarios](/scenarios/collaboration/sharing-scenarios.md) — Control who has Edit access
* [Commenting](/scenarios/collaboration/commenting.md) — Coordinate via comments
* [Notifications](/admin-capabilities/notifications.md) — Stay informed of approvals and invitations


---

# 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.agentnoon.com/scenarios/collaboration/co-editing.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.