> ## Documentation Index > Fetch the complete documentation index at: https://docs.findtempo.co/llms.txt > Use this file to discover all available pages before exploring further. # Reviewing CRM updates > How Tempo proposes CRM field updates with evidence, and how you approve, reject, or edit them in Slack, on the deal page, or from your AI platform, and revert them from your AI platform. Tempo reads your meetings, email, and other connected sources and proposes new values for the CRM fields it tracks. Each proposal carries the evidence behind it. A field's update behavior determines whether approval is needed. You can read organization field proposals on every deal in your organization. Only the deal owner or an organization admin can edit, approve, or reject them, in the app, in Slack, or over MCP. Personal field proposals remain private to their owners, and only the owner can approve or reject them. A deal with no owner has no one to approve or reject its proposals, organization admins included. Only fields set to **Automatic** apply values on those deals. On a Salesforce deal, Tempo writes an approved value through the Salesforce connection of the person who approves it. Salesforce shows that person as the editor. An organization admin who approves on a teammate's deal needs their own Salesforce connection. ## What an update is An update is a proposed change to one field on one opportunity. It shows: * The **field** and the **proposed value**. * The **current value** in your CRM, so you can compare. * The **reason**, with a citation to the artifact that produced it. * A **write mode** when the field appends or prepends instead of replacing. An update has one of three statuses: **Pending**, **Approved**, or **Rejected**. Approving writes the value to your connected CRM. Rejecting discards it. ## Which fields produce updates Each field has an **update behavior** that an organization admin sets in **Settings → Field Management**: | Update behavior | What happens | | - | - | | **Suggest** | Tempo proposes the value. It waits as Pending until someone approves it. | | **Automatic** | Tempo writes the value to your CRM without a review step. The update appears as Approved. | | **Manual** | Tempo proposes nothing for the field. | > [!WARNING] > > Fields set to **Automatic** apply without review. When your organization allows per-user field settings, you can also set your own fields to Automatic, which auto-approves proposals on your own deals. Check [Fields and CRM updates](https://docs.findtempo.co/admin/fields.md) before you rely on a field being reviewed. Tempo does not generate automatic updates on closed opportunities, and it skips batches that come only from artifacts older than 30 days. Those proposals stay Pending or are not created. ## Approve from Slack When an organization admin turns on **Notify deal owners to approve CRM updates** in the Slack settings, Tempo sends you a direct message for each proposal on a deal you own. You can change where yours go, or turn them off, under **Deal update approvals** on your Profile. The message shows the field, the value being replaced, the proposed value, and a **Sources** button that opens the cited evidence. Three buttons act on it: * **Approve** writes the value to your CRM. * **Reject** discards the proposal. * **Edit** opens **Edit update**, where you change the value before saving it. The message links to the deal's Updates tab in the Tempo app when you want the full picture. ## Review on the deal page Open an opportunity in the Tempo app and select the **Updates** tab. A count on the tab shows how many proposals are pending. **1. Read the proposal** Each row shows the field, the proposed value, and the reason. Click **Show current** to compare with the value in your CRM. **2. Change the value if needed** Click **Propose edit** to replace the proposed value with your own before approving. **3. Approve or reject** Approve or reject one field, a selection of fields, or every field in the update. If the tab reads **Select fields to update**, no field on this organization has Suggest or Automatic update behavior yet. Pick fields to turn generation on, or ask an admin. ## Revert an approved update Reverting returns an approved update to Pending and restores the field's previous value. Ask your AI platform to revert it. See [Review from your AI platform](#review-from-your-ai-platform). Revert acts only on approved updates. It cannot return a rejected proposal to Pending. To set a field back to an earlier value directly, use the field's history. On the deal's **Fields** or **Updates** tab, click the clock icon labeled **Field history**. Under **Change History**, click **Revert** on an earlier value, then confirm. ## Act from the Opportunities table In the Opportunities table, right-click a field cell to open **Field update actions**: * **Review update** opens the pending proposal for that cell. * **Check for update** asks Tempo to look for a new value for that field on that deal, using the evidence it has. It appears only on fields Tempo can generate updates for. * **Edit field** opens the field's definition. ## Review from your AI platform Over MCP, your platform lists proposals and acts on them when you ask. ```text wrap theme={null} Show me pending CRM updates across my open deals. Include the field, proposed and current values, and the reason. ``` ```text wrap theme={null} Approve the Champion update on [Tecca Chairs]. Reject the Amount update. ``` ```text wrap theme={null} Revert the close date update I approved on [Tecca Chairs] yesterday. ``` ```text wrap theme={null} Create a pending update on [Tecca Chairs]: set Next Step to "Legal review in progress". Do not approve it. ``` Lists cover every deal in your organization, not only the deals you own. To act on a proposal, you must own the deal or be an organization admin. Ask your platform to show a proposal and its evidence before acting. A proposal it creates lands as Pending unless you ask for approval. Cross-deal lists default to open, non-renewal deals updated in the last 30 days. See the [MCP tool reference](https://docs.findtempo.co/developers/mcp-tools.md) for `list_deal_updates` and `manage_fields`. ## When a value exceeds the CRM field limit Your CRM can reject an approval when the final value is too long. Tempo reports the field, the merged character count, and the maximum length. The merged value includes the existing CRM value when the field's write mode is **Append** or **Prepend**. **1. Read the error** Note the field name, merged character count, and maximum length. **2. Reduce the final value** Shorten the existing value in your CRM, or ask an admin to review the field's write mode in **Settings → Field Management**. **3. Retry the approval** Approve the proposal again. ## When a source needs reconnecting A banner such as **Reconnect Granola** means a connected source has stopped syncing. No new context flows in from it and no new proposals come from it until you reconnect. Click **Reconnect** and authorize the source again. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.