> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sphinx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Review and accept knowledge changes

> Inspect a Sphinx knowledge pull request, review page differences, and accept or reject the proposal.

Sphinx proposes knowledge updates for human review. These proposals are sometimes called knowledge **pull requests (PRs)**. Find them under **Review Changes → Proposed Context Changes**.

## Before you start

Select the correct workspace and have a proposal ready to review. You should understand the source material or involve the person responsible for the affected definitions.

## Open a proposal

Open **Review Changes**, then choose a proposal from **Suggested**. Use **Accepted** and **Rejected** to find earlier decisions. You can also reach a proposal from its ingest job's **Review Changes** action.

Read the **Ingest agent summary** and the **Overview**. Related page changes are organized into change groups to help you review a shared decision together.

![Demo account change proposal with synthetic data showing its title, Ingest agent summary, and Overview and Changes navigation](https://mintcdn.com/sphinx-977f1673/O9wCzUTcMLhLJ368/images/ui/review-overview.jpg?fit=max\&auto=format\&n=O9wCzUTcMLhLJ368\&q=85\&s=af8465c04ae63938de09899eff640e8a)

A proposal summarizes the update and groups related page changes.

## Review the differences

1. Open a change group or the **Changes** view. Select **All pages** to review the complete proposal.
2. Compare the **Before** and **After** blocks. Check definitions, calculations, exceptions, dates, and citations.
3. Use **Show unchanged blocks** or **Expand** when you need surrounding context.
4. Mark a page **Viewed** to track your review. This is a review marker, not an acceptance decision.
5. If a proposed page change should not be applied, select that page's **Reject** control. Its description is **Leave this page as it is now**. Use **Edit** if you need to correct the proposal before accepting it.

Use **Ask about this change** when you need an explanation of the proposal. Check supporting evidence before making the final decision, especially when the update introduces or changes a controversy.

> [!NOTE]
>
> Change-group filters help you navigate the proposal. Review the full set of page decisions before submitting.

## Submit the decision

Open **Submit** at the top of the proposal and choose:

| Decision | Result |
| - | - |
| **Accept** | Applies the proposal to the knowledge base, respecting page-level rejections. |
| **Reject** | Closes the proposal without applying any of it. |

Click **Submit** in the decision panel to finalize. Use **Cancel** to return to review without submitting.

## Verify the result

Return to **Review Changes** and find the proposal under **Accepted** or **Rejected**. After acceptance, open the affected pages in **Browse Knowledge** and check that the final wording matches your decision.

If the proposal documents unresolved disagreements, follow up in [Controversies](https://docs.sphinx.ai/knowledge-base/controversies.md). Accepting a proposal that records a disagreement does not establish which competing business rule is correct.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.