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
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Essentials, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
| User Permissions Needed | |
|---|---|
| To install packages: | Download AppExchange Packages |
- Go to AppExchange.
- Browse or search for a solution.
-
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.
- Select your environment type: production or sandbox.
- Enter any requested information, agree to the terms and conditions, and then click Confirm and Install.
- Enter the requested information.
- If the package is password-protected, enter the password you received from the provider.
- To review the package components, click View Components.
- 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.
- 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.
