---
schema_version: "1"
id: 8c301f39ec81026840b745110dd881da2844bfc8d51cfecff7776c98e29c85fd
title: Enable Integrations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/enable_integration_assets.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.enable_integration_assets.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 08296eddb7b34e13a4d65d1b5ae1a3dcebf8e1793d71e829935d7e56ff4e0151
description: An integration is a prebuilt app or a configurable example. Integrations simplify the business workflow implementation by allowing external systems to easily integrate with the Salesforce Cloud apps. An integration can depend on several other apps that are necessary to complete a business use case. For example, an integration app that syncs orders between SAP S/4HANA and Salesforce Manufacturing Cloud has a related System API app to connect Salesforce to the SAP S/4HANA system. Enabling an integration configures and deploys an instance of the integration and its dependent apps in your MuleSoft instance. Enable an integration multiple times to create multiple instances of the same integration.
products:
  - Industry Solutions
  - MuleSoft
release: "264"
---
# Enable Integrations

An integration is a prebuilt app or a configurable example. Integrations simplify the business workflow implementation by allowing external systems to easily integrate with the Salesforce Cloud apps. An integration can depend on several other apps that are necessary to complete a business use case. For example, an integration app that syncs orders between SAP S/4HANA and Salesforce Manufacturing Cloud has a related System API app to connect Salesforce to the SAP S/4HANA system. Enabling an integration configures and deploys an instance of the integration and its dependent apps in your MuleSoft instance. Enable an integration multiple times to create multiple instances of the same integration.

### 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: all editions</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="d1902e54">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d1902e54 ">To enable integration assets:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d1902e54 ">
              <p>Salesforce Administrator profile</p>
              <p>AND</p>
              <p style="margin-bottom:0;">MuleSoft Administrator profile</p>
            </td>

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

1. In Setup, find and select **MuleSoft Direct**.
2. On the MuleSoft Direct Setup page, in the Available Assets area, from the list of available integrations, go to the integration that you want to enable, and then click **Enable**.
    
    - Some integrations have prerequisites that you must complete before you enable. To see the prerequisites of an integration that you want to enable, click **View Prerequisites**.
    - Some integrations use third-party connectors. To know more about these connectors, click **View Terms and Conditions**.
3. Enter a display name for the integration.
    
    A display name is how you want the enabled integration instance to be referenced in a Salesforce org.
4. Enter the app name.
    
    Make sure that the app name is unique to your MuleSoft instance.
5. Select the business group that you want to enable the integration for.
6. Select the environment where you want to enable the integration.
7. Select the deployment target where you want to deploy the integration.
8. Click **Next**.
9. Enter configuration details for each of the dependent apps.
    
    To reuse the configuration settings of a saved connection, click **Use a saved connection** and select the connection from the Connection Name dropdown.
10. To save the connection configuration details, click **Save this connection**, enter a display name, and save your work.
    
    The connection is saved in the Connection section of the Home page. You can reuse the saved connection to configure a dependent app or another integration app without reentering the configuration details.
11. If needed, add or remove additional parameters:
    1. Click **Add Additional Parameters**.
    2. Provide a key and a value.
        
        If you're deploying the integration to CloudHub 2.0, you can hide the parameter value on the Anypoint Runtime Manager by selecting **Hide value on Anypoint Platform**.
    3. To add more parameters, click **Add New**.
    4. To remove an additional parameter, click the delete icon next to Value.
12. Click **Proceed** and wait for the enablement process to be completed.

A named credential is created for the enabled integration instance, and the deployed integration instance is available in the Applications menu of MuleSoft Runtime Manager. You can now extend the app in MuleSoft Anypoint Platform.

#### See Also

- [Manage Connection](https://help.salesforce.com/s/articleView?id=ind.manage_connection.htm&release=264.0.0&type=5 "View the details of a saved connection, edit a connection to change the authentication settings required to connect to an external system, or delete a connection.")