Change review
Change review holds edits to protected files for approval before they apply, keeping sensitive files under human control.
Category
Product feature
See all terms
What is change review?
Change review holds an edit to a protected file for a decision before it applies, so a human accepts or discards it instead of it landing automatically. It happens in the Changes tab, split into changes still awaiting a decision and ones already reviewed. It applies to two kinds of edits: changes an automated source produces, and changes made directly through the platform, MCP, or the API.
Why change review exists
Not every file should update itself as soon as connected data changes. Some files need automated maintenance to keep them current, while others need a person to sign off before an edit reaches something the whole team relies on. Change review lets everything else stay self-maintaining while flagged files keep a human in the loop. Both automated changes from a synced source and manual edits show up the same way once review is turned on, so a reviewer sees every path a file could change through in one place.
How does change review work?
A member with access management permissions turns on Require review for a specific file. From that point, any change to it lands in the Changes tab instead of applying immediately, sitting there with an explanation, its status, when it was created, what triggered it, and a diff of what changed. A reviewer accepts a change to apply it to the file, or discards it, which requires giving a reason. If a file gets deleted while a change is still pending, that change cancels automatically rather than needing anyone to reject it. Every reviewed change becomes part of the file's history in the context repository.