Reviewing

Accepting and Rejecting Changes

How much review a change needs is up to you. Each folder's Local edits setting has three modes, set in the folder controls.

Needs approval

Nothing lands without you. Every change waits as a blue pending proposal until you accept or reject it.

• Accept applies the change and attributes it to the contributor.
• Reject dismisses it permanently. It won't come back, even after reopening the app.

Auto-accept

Everything lands on its own, but stays marked until you read it. Landed-but-unread changes show as green marks in the document and green counts in the files panel.

A green mark clears when you've actually seen it: scroll it into view and it fades. You can also hide a change for the current session, or press Mark file caught up to clear a whole file durably. Until then, each unread change stays revertable from its pill.

Nothing is ever lost either way: every version is in Version history.

Hybrid

Stet grades each incoming change and decides per change:

• Trivial and normal changes land on their own, marked until read, like Auto.
• Significant changes — a changed number, date, or dollar amount, a deleted sentence, a flipped negation, and so on — wait for your approval, like Needs approval.

The grading is deterministic and runs entirely on your machine; no AI is involved. The full signal table is in How Stet Grades Changes. Hybrid requires the Review signals setting to be on, and a file that already has a pending proposal always queues new changes rather than landing them.

Where to set it

Open the folder controls (right-click a folder > Folder settings) and set Local edits to Needs approval, Hybrid, or Auto-accept. Subfolders inherit from their parent unless you set them explicitly. Changes from collaborators have their own lanes — see Review Policy by Source.