---
schema_version: "1"
id: 8759433884687fb72172ff6d6d609fd3e9a1e1e6b89f327d9a05fb09964b91f6
title: Install a Managed Package
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/distribution_installing_packages.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.distribution_installing_packages.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0544cc38e18c2e5473cf6aaa425231d223760cddbff36c261bb1e4bd99f6dd0a
description: Installing a managed package from AppExchange in your Salesforce org is straightforward. First, install the managed package, and then configure it for your environment and users.
products:
  - Salesforce Platform
  - Cross Cloud
release: "264"
---
# Install a Managed Package

Installing a managed package from AppExchange in your Salesforce org is straightforward. First, install the managed package, and then configure it for your environment and users.

### 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 and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Essentials</strong>, <strong>Group</strong>, <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> 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="d74793e83">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d74793e83 ">To install packages:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d74793e83 ">Download AppExchange Packages</td>

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

1. Go to [AppExchange](https://appexchange.salesforce.com/).
2. Browse or search for a solution.
3. Click **Get It Now** on the solution’s listing page.
    
    If the listing doesn’t have a **Get It Now** option, it's a solution that you can download and use outside of Salesforce. For more information, contact the provider.
4. Select your environment type: production or sandbox.
5. Enter any requested information, agree to the terms and conditions, and then click **Confirm and Install**.
6. Enter the requested information.
7. If the package is password-protected, enter the password you received from the provider.
8. To review the package components, click **View Components**.
9. In Enterprise, Unlimited, Performance, and Developer Editions, select which user type can access the package. For more details, review [Determine Which Users Can Access a Package](https://help.salesforce.com/s/articleView?id=xcloud.pkg_subscriber_determine_access.htm&type=5&language=en_US).
10. Click **Install**.

When you install a component that contains Apex, the unit tests contained in the new package, and all unit tests for your org are run. If a unit test relies on a component that is initially installed as inactive, the unit test fails. You can select to install regardless of unit test failures.

If the package includes post-installation instructions, they’re displayed after the installation is completed. Before you deploy the package to your users, make any necessary changes for your implementation.

If the package includes permission sets, assign the included permission sets to the users who need them. You can't edit permission sets that are included in a managed package, but you can clone the permission set, or create your own. Permission sets you create or clone aren’t affected by package upgrades.