---
schema_version: "1"
id: add43b91b866d954cc83be7118d521592f2506998e1e99447135ddecec89741f
title: Deploy a Change Set in Salesforce Spiff
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/sales/264-0-0/spiff_deploy_change_sets.md
canonical_url: https://help.salesforce.com/s/articleView?id=sales.spiff_deploy_change_sets.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 4864dcda72f0f0139246e960e38822d4e355e8cc48e3bdb8b9076bbacbe6d830
description: After you validate and approve your changes, deploy them to the production environment. You can deploy only one change set at a time. Deploy subsequent change sets only after the prior deployment completes.
products:
  - Sales Cloud
  - Sales Enablement
release: "264"
---
# Deploy a Change Set in Salesforce Spiff

After you validate and approve your changes, deploy them to the production environment. You can deploy only one change set at a time. Deploy subsequent change sets only after the prior deployment completes.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available for an additional cost in: <strong>Professional</strong> Edition with Web Services API Enabled</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d78694e81">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d78694e81 ">
              <p style="margin-bottom:0;">To deploy change sets in Salesforce Spiff:</p>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d78694e81 ">
              <p>A Spiff <a href="https://help.salesforce.com/s/articleView?id=sales.spiff_users_roles_and_permissions.htm&amp;release=264.0.0&amp;type=5" title="Give users the appropriate level of access so they can be successful in Salesforce Spiff, and enforce the principle of least privilege. Assign a default role to each user, or create custom roles with access to specific Spiff functionality.">user role</a> with these permissions turned on.</p>
              <ul>
                <li>Change Sets: View</li>

                <li>Change Sets: Deploy</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-sales-sales_performance_management-264-0-0-production-enus/b1f2feb4-26b8-444f-97f7-be2349869d93/images/icon_note.png)

Note To prevent data collisions, you can’t modify the target environment or access Designer while a deployment is in progress. Because you can’t undo a deployment after it starts, verify all changes before you begin. You can’t deploy change sets from multiple sandboxes to a single parent environment.

1. In the parent environment, go to **Admin** and select **Settings**.
2. Under Environments, select **Inbound Change Sets**.
3. In the Name column, click the change set to deploy.
    
    You can only deploy a change set that you’ve approved and with the status Ready to Deploy.
4. Click the **History** tab to review the change set's workflow history, including Submission, Validation, and Approval steps.
    
    This is useful for compliance audits and for confirming the correct approvals are in place.
5. Click **Deploy Changes**.
    
    If the deployment fails, Spiff notifies all users who have Read permission in Spiff Designer or Read permission for change sets. You can turn off these notifications in your email and in-app notification settings.
6. Go to Spiff Designer in the parent environment and wait for the page to load.
    
    Complete this step to finalize the deployment.
    
    After you deploy a change set, Spiff sends an email that tells you to access Designer and finalize the deployment. This email goes to all users with Read permission in Spiff Designer or Read permission for change sets, even if you've turned off Spiff email notifications in your settings. Accessing Designer is necessary to trigger the remapping of formulas and to ensure calculations run correctly. After you deploy a change set to the parent environment, you can’t revert the changes.