# Comments and presence (/docs/guides/comments)

## Comments [#comments]

The entry editor's sidebar has the entry's **comments**, for the people working on it: a question about the intro, a note for the translator, feedback before publishing.

- A comment is about the **whole entry** or **one field** (pick it under **About**), and others **reply** to it. Replies stay one level deep: replying to a reply joins its thread.
- **Resolve** a thread once it's dealt with; it folds away (**Show resolved** brings it back) and can be reopened. Its author and anyone who can edit the entry can resolve it.
- Everyone who can read the entry can comment, readers included, so a reviewer doesn't need edit rights. A comment can be deleted by its author and by admins; deleting a thread deletes its replies.
- Comments belong to the entry in its environment. They are never part of its content, its history, promotion or the delivery API, and they go when the entry is deleted (also to the trash).
- New comments from others show up within half a minute while the entry is open.

Agents read and write them with `GET` and `POST …/entries/{id}/comments` (`{ "body", "field"?, "parentId"? }`), resolve with `PATCH …/comments/{commentId}` (`{ "resolved": true }`) and delete with `DELETE …/comments/{commentId}`.

## Who else is here [#who-else-is-here]

While you have an entry open, the toolbar shows who else has it open too. When one of them has **unsaved changes**, it says so: whoever saves second gets a [conflict](/docs/guides/publishing) and has to reload, so agree on who edits, or save often.

The editor checks in every 20 seconds; someone who closed the entry or went quiet for about a minute is gone from the list.