Track changes

Track changes lets a collaborator propose edits to a piece without altering it. Each proposed change is attributed and waits for the author to accept or reject it. The piece itself stays clean until the author decides, so nothing is changed behind anyone’s back.

This is different from version history, which snapshots the whole document. A proposed change is small and surgical: a few words added here, a sentence struck there.

Turning it on

Track changes is off by default. The author turns it on per piece from the Proposed changes panel in the More menu. While it is off, editing works the way it always has.

Inviting a collaborator

In the same panel, invite a collaborator by their Inkbreaker username and choose their role:

• A commenter can leave inline comments.
• An editor can also propose changes.

A pending invitation shows Invitation sent until it is accepted. You can change a collaborator’s role or remove them at any time. Removing a collaborator does not erase changes they already proposed; those still wait for your review.

Suggesting an edit

With track changes on, turn on Suggesting. From then on your edits do not change the words on the page. Instead, new text appears as a green underline and removed text stays in place with a red strikethrough, each tagged with who made it. When you are ready, choose Propose changes to send them to the author. Your suggestions live with your working copy, never in the published piece.

Reviewing changes

The author sees each proposed change in the Proposed changes panel, with who proposed it and a preview of the words removed and added. Selecting a change jumps to where it sits in the piece.

Each change has Accept and Reject. Accepting applies it to the piece; rejecting discards it and leaves the writing untouched. There are Accept all and Reject all for clearing the whole list at once. Before any review action a version snapshot is taken, so accepting changes is always reversible from the version browser.

If two proposed changes overlap the same passage, the panel flags them so you can review carefully. Changes are never merged automatically; the author always decides.

Notifications

When a collaborator proposes changes, the author gets a single notification, even if the collaborator saves several times in a row. When the author accepts or rejects a change, the collaborator is told plainly.