> For the complete documentation index, see [llms.txt](https://docs.slapfive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slapfive.com/integrations/salesforce/synchronize-data-between-salesforce-and-slapfive/allow-the-integration-user-to-update-closed-opportunities.md).

# Allow the integration user to update closed Opportunities

### Why this may be needed

The Revenue Influence Reporting in the SlapFive Salesforce App uses the [custom objects SlapFive Customer Influence and SlapFive Customer Influence Activity](https://docs.slapfive.com/integrations/salesforce#custom-objects), as well as the [Opportunity custom fields described here](https://docs.slapfive.com/integrations/salesforce#custom-fields). It is not uncommon for revenue influence events to be recorded after the Opportunity has been closed. If your company has an Opportunity Validation Rule that prevents any updates to closed Opportunities, then the SlapFive integration cannot create or update the custom objects. The solution is to modify the Opportunity Validation Rule to allow thd Integration User to update closed Opportunities.

### Add an Automation Bypass to the Opportunity Validation Rule

Modify the existing Opportunity validation rule to **exclude trusted automation**, such as an integration user or permission set.

#### Step 1: Create a Permission Set

1. Go to **Setup → Permission Sets**
2. Click **New**
3. Name it something like:
   * `Bypass Closed Opportunity Validation`
4. Save

No object permissions are required.

#### Step 2: Update the Validation Rule

Edit the existing Opportunity Validation Rule and add a condition to exclude users with this permission set.

**Example logic:**

```
AND(
  IsClosed = TRUE,
  NOT($Permission.Bypass_Closed_Opportunity_Validation)
)
```

This means:

* The rule still blocks edits to closed Opportunities
* Except when the user has the bypass permission

#### Step 3: Assign the Permission Set

Assign the permission set to your integration user.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.slapfive.com/integrations/salesforce/synchronize-data-between-salesforce-and-slapfive/allow-the-integration-user-to-update-closed-opportunities.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.