# Suggest changes

Track changes in a shared project: suggest edits instead of making them, review them in the comments pane, and accept or reject them.

In **Suggesting** mode, your edits become suggestions that an owner or editor accepts or rejects. It's the way to propose changes to a co-author's section, or to mark up a draft without rewriting it yourself.

## Editing and Suggesting

Owners and editors switch the editor between **Editing** and **Suggesting**:

- In **Editing**, what you type changes the text straight away, as in any project.
- In **Suggesting**, every insertion and deletion you make becomes a suggestion.

Reviewers always suggest: everything a reviewer types is a suggestion. They can also comment. Viewers can't suggest.

## What suggestions look like

- **Inserted text** has a background in the colour of the person who suggested it.
- **Deleted text** is struck through.

Suggestions sync live like any other edit. Everyone sees them appear as the person types.

## What's in the file

The files in the project hold the suggested version of the text until someone accepts or rejects it:

- A pending insertion is already in the file. The editor shows it with the author's colour behind it.
- A pending deletion is already gone from the file. The editor still shows the deleted text, struck through, so you can see what was removed. That struck-through text is only on screen.

The file never contains tracking markup. Who suggested what is kept with the shared project, not inside the file.

Because the file holds the suggested text, the compiled PDF shows pending suggestions: new text appears and deleted text is gone. Other editors, scripts and Git see the same file.

When you compile or export while suggestions are still waiting for review, Oleafly tells you how many the project has, so nobody submits unreviewed changes by accident.

## Review suggestions

Each suggestion appears in the **Comments** pane with its author and the time it was made. Owners and editors decide what happens to it:

- **Accept** keeps the text as it is and removes the marking.
- **Reject** puts the original text back in the file. A suggested insertion is removed, and suggested deleted text returns.

To handle a whole file at once, use **Accept all** or **Reject all** for that file.

The person who made a suggestion can withdraw it. That puts the original text back, the same as a rejection.

## Discuss a suggestion

A suggestion can carry a comment thread. Reply to it in the **Comments** pane to explain the change or ask about it before anyone accepts it. [Comments](/docs/collaboration/comments/) covers replies, mentions and resolving.