# Suggest changes

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

In **Suggesting** mode, your edits become suggestions that an owner or editor accepts or rejects. Use it 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 between **Editing** and **Suggesting** on the project toolbar, just before the compile controls. The switch is there only in a shared project, and **Editing** is the default.

- 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. So does a change Oleafly saves to a file for you, such as an edit from the AI assistant.

Reviewers always suggest. The toolbar shows **Suggesting** for them, and they can't switch it off. Everything a reviewer types becomes a suggestion, and they can also comment.

Commenters and viewers can't suggest, and they don't see the switch. Commenters can still select text and comment on it. [Roles](/docs/collaboration/sharing/#roles) lists what each role can do.

## What suggestions look like

- **Inserted text** has a background in the colour of the person who suggested it.
- **Deleted text** stays on screen where it was, struck through, in that person's colour.

Hover over a suggestion to see who made it, such as "Alice Chen suggested adding this". Select it to open its card in the **Comments** pane.

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, Oleafly tells you how many there are: "This project has suggestions waiting for review: 3. The PDF shows them as if they were accepted." You see it once, and again only when the number changes, so nobody sends off unreviewed changes by accident.

## Review suggestions

Each suggestion has a card in the **Comments** pane, in the section for its file. The card shows who suggested it and when, with the text marked **Added** or **Deleted**. Select the text on the card to jump to it in the editor. A number beside each file's name says how many suggestions in that file are waiting.

Owners and editors decide what happens to each one:

- **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** at the top of that file's section. **Reject all** asks first, because it puts the original text back for everyone.

A reviewer can **Withdraw** a suggestion of their own. Oleafly asks "Withdraw this suggestion?", then puts the original text back, the same as a rejection. Owners and editors reject their own suggestions instead.

## Discuss a suggestion

Each suggestion card has a **Reply** box. Use it to explain the change, or to ask about it before anyone accepts it. The first reply starts a comment thread on the suggested text, and later replies join that thread. Type `@` to mention someone.

Owners, editors, reviewers and commenters can reply while comments are on for the project. [Comments](/docs/collaboration/comments/) covers mentions, resolving and turning comments off.
