---
title: "Salesforce Integration"
slug: "salesforce-integration"
description: "Learn more about the requirements to configure the Fullcast change owner lightning action in Salesforce."
status: "update"
updated: 2025-10-16T18:56:52Z
published: 2025-10-16T18:56:52Z
canonical: "support.fullcast.com/salesforce-integration"
stale: true
---

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

# Salesforce Lightning Actions

Fullcast's lightning actions leverage roles and coverage assignments in Fullcast to control visibility and access for ownership changes. The change owner action provides controls on which users are eligible for account ownership, which roles and users can use the change owner action, and the scope and timing of the changes.

## Configuration

Configure access to the Fullcast change owner action button on various layouts in the Salesforce settings.

## Access requirements

Standard users must meet the following requirements to access the change owner action:

> [!NOTE]
> Note
> 
> Tenant admins have access to the change owner action regardless of their coverage assignment.

- An assignment to the segment or territory where the account is listed.
- The territory coverage assignment role must have **Read Write** permissions for **Territory Account Operations**. Refer to [Create normal and temporary assignments](/v1/docs/coverage-assignments#normal-and-temporary-coverage) and [configure user permissions](/v1/docs/configure-user-permissions).

## Account assignment requirements

The following are required when you assign accounts:

- The user must have a coverage assignment for the role selected in the custom metadata field `Role_Name`.
- The selected role in the custom metadata must be enabled for export in Fullcast.
- To include multiple roles for assignments, such as account executive and sales manager, separate each role with a comma.

## Commit flag settings

Setting the commit flag to `True ` or `False` impacts how and when the change will occur. Configure the **commit** and **proposed** option at the Salesforce instance level. Only one selection can be made and it applies universally.

### **Commit**

- **Set flag:** `True`—changes are permanent in both Salesforce and Fullcast.
- **Immediate changes:**
  - The account owner changes in Salesforce.
  - The account moves to the new territory in Fullcast.
  - The account team member is deleted in Salesforce.
- **Changes during the next import/export:**
  - The account team and Fullcast territory member updates in Salesforce.
  - The account owner field (imported from SFDC) updates in Fullcast.

### **Proposed**

- **Set flag:** `False`—changes are proposed in Fullcast for review before finalization.
- **Immediate changes:**
  - The owner change appears as a proposed account move to the proposed owner’s territory in Fullcast (the owner does not change on the account in Salesforce).
- **Changes during the next import/export:**
  - After the proposed owner change (account move) is reviewed and committed in Fullcast, the change is pushed to Salesforce.
  - The account team and Fullcast territory member is updated to reflect the account move.
  - The account owner is updated in Salesforce if you have a flow set up to write the account owner based on the territory assignment that Fullcast writes to the account team or Fullcast territory member.