Overview
Change reviews let you approve or discard changes to a file before they’re applied to your context repository. Use them to keep sensitive files under human control while everything else stays self-maintaining. Reviews happen in the Changes tab. Select a change from the list to review it. Changes that conflict with the current file can also be resolved there, by selecting which edits to keep or by resolving via chat.Requiring review
Open a file’s settings and turn on Require review to hold its content changes for review instead of applying them automatically. Requiring review is available to members who can manage access on the file or folder.Protected folders
In Context, open a folder’s settings and turn on Require review. Content changes to files in that folder and its subfolders are then held for review, including changes to files added later. Files and subfolders inherit the requirement. If a parent folder requires review, change the setting on that parent; it cannot be turned off on a child. Turning it off on a folder does not remove review requirements set separately on files or subfolders. In Changes, the lock icon also marks files that inherit the review requirement from a parent folder. Protection also prevents deleting protected files or moving a folder in a way that would remove protection from its files. For example, moving a subfolder outside its protected parent is blocked if any files would lose their protection. An empty protected folder can still be deleted.Reviewing a change
The Changes tab has two lists:- To review: changes waiting for a decision, including changes that depend on an earlier unapproved change
- Completed: changes that were approved, discarded, or cancelled
- Automated change: produced from a connected source
- Manual update: a direct write to the file, made in the platform or through MCP or the API
Filtering changes
Use the list menu to switch between To review and Completed, or show only Approved, Discarded or Cancelled changes. The filter menu narrows changes by date, author, client or data source type. Authors include people and automated updates; clients include AI tools and API keys. Data source filters match a type, such as Slack, rather than an individual connection. Completed shows the last 30 days by default. Change the date range or clear it to see older changes. Some combinations of filters require a date range. Filters are kept in the page URL, so reloading or sharing the link preserves the view. If no changes match, select Clear filters to widen the list.Waiting changes
A change can build on another change that has not been approved yet. It appears in To review with a Waiting status and is included in the navigation count. The change summary links to the earlier changes under Depends on. It also shows the number of depending changes. Open that list to inspect later changes that depend on the selected change, directly or through other changes. A waiting change cannot be approved until the changes it depends on have been applied. It can still be discarded.Approving or discarding
For a change that’s in review, you can:- Approve change: the selected edits are applied. When there are no conflicts, the whole change can be approved without making individual file decisions.
- Discard change: the change isn’t applied. A reason is required and kept on the record for that change.
Conflict resolution
When a change conflicts with the current file, review its proposed edits directly in Changes.1
Choose the edits to keep
Expand a file and use Keep or Discard for each edit. To decide on a whole file, open its menu and choose Keep all edits in this file or Discard all edits in this file.
2
Adjust decisions if needed
Use Undo on an edit to choose again, or Undo decisions in the file menu to reset the file’s decisions. These choices do not change the repository until approved.
3
Approve the result
Decide on every edit in the conflicting change, then choose Approve change. If all proposed edits are discarded and nothing remains to apply, use Close change instead.