Newer Version Available

This content describes an older version of this product. View Latest

After Installing a Package

After installing an app from Lightning Platform AppExchange, manage it like you manage other standard apps such as Sales or Service.

Manage Installed Packages

Manage packages installed in your Salesforce org, including assigning licenses to users, uninstalling packages, and exporting package data.
Available in: Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Essentials, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions

User Permissions Needed
To uninstall packages: Download AppExchange Packages
To assign licenses for a managed package: Manage Package Licenses
To download or delete the export file for an uninstalled package: Download AppExchange Packages

Salesforce only lists license information for managed packages. For unmanaged packages, the license-related fields, such as Allowed Licenses, Used Licenses, and Expiration Date, displays the value “N/A.”

Note

Using this list, you can:
  • Click Uninstall to remove the package and all its components from your Salesforce organization.
  • Click Manage Licenses to assign available licenses to users in your organization.

    If you purchased a site license or if the managed package is not licensed, Salesforce assigns licenses to all your users and you can’t manage licenses. Your users can use the package as long as they have the appropriate permissions.

    Note

  • Click Become Primary Contact to update the current contact for the installed package to your username. This contact name displays for the package publisher from the Push Package Upgrade page. Initially, it’s set to the name of the person who installed the package. If you have Download AppExchange Packages permission and aren’t the current primary contact, this option is enabled.
  • Click Configure if the publisher has included a link to an external website with information about configuring the package.
  • Click the package name to view details about this package.
  • View the publisher of the package.
  • View the status of the licenses for this package. Available values include:
    • Trial
    • Active
    • Suspended
    • Expired
    • Free

    This field is only displayed if the package is managed and licensed.

  • Track the number of licenses available (Allowed Licenses) and the number of licenses that are assigned to users (Used Licenses).
  • View the date your licenses for this package are scheduled to expire.
  • View the date your licenses were installed.
  • View the number of custom apps, tabs, and objects this package contains.
  • See whether the custom apps, tabs, and objects count toward your organization’s limits. If they do, the box in the Limits column is checked.

If you have not installed a licensed managed package, the Publisher, Status, Allowed Licenses, Used Licenses, and Expiration Date fields do not appear.

Note

After an uninstall, Salesforce automatically creates an export file containing the package data, associated notes, and any attachments. When the uninstall is complete, Salesforce sends an email containing a link to the export file to the user performing the uninstall. The export file and related notes and attachments are listed below the list of installed packages. We recommend storing the file elsewhere because it’s only available for a limited time after the uninstall completes. Using this list, you can:
  • Click Download to open or store the export file.
  • Click Del to delete the export file.
Expired Managed Packages and Sharing Rules
If a criteria-based sharing rule references a field from a licensed managed package whose license has expired, (expired) is appended to the label of the field. The field label is displayed in the field drop-down list on the rule’s definition page in Setup. Criteria-based sharing rules that reference expired fields aren't recalculated, and new records aren't shared based on those rules. However, the sharing of existing records prior to the package's expiration is preserved.

Uninstalling a Package

Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
Available in: Essentials, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions

User Permissions Needed
To uninstall packages: Download AppExchange Packages

You can remove any installed package, including all its components and all data in the package. Also, any custom fields, links, or anything else you added to the custom app after installation are also removed.

To remove a package:
  1. From Setup, enter Installed Packages in the Quick Find box, then select Installed Packages.
  2. Click Uninstall next to the package that you want to remove.
  3. Select Yes, I want to uninstall... and click Uninstall.
  4. After an uninstall, Salesforce automatically creates an export file containing the package data, associated notes, and any attachments. When the uninstall is complete, Salesforce sends an email containing a link to the export file to the user performing the uninstall. The export file and related notes and attachments are listed below the list of installed packages. We recommend storing the file elsewhere because it’s available for only two days after the uninstall completes, then it's deleted from the server.

    If you reinstall the package later and want to reimport the package data, see Importing Package Data.

    Tip

Notes on Uninstalling Packages

  • If you’re uninstalling a package that includes a custom object, all components on that custom object are also deleted. Deleted items include custom fields, validation rules, s-controls, custom buttons and links, workflow rules, and approval processes.
  • You can’t uninstall a package whenever a component not included in the uninstall references any component in the package. For example:
    • When an installed package includes any component on a standard object that another component references, Salesforce prevents you from uninstalling the package. An example is a package that includes a custom user field with a workflow rule that gets triggered when the value of that field is a specific value. Uninstalling the package would prevent your workflow from working.
    • When you have installed two unrelated packages that each include a custom object and one custom object component references a component in the other, you can’t uninstall the package. An example is if you install an expense report app that includes a custom user field and create a validation rule on another installed custom object that references that custom user field. However, uninstalling the expense report app prevents the validation rule from working.
    • When an installed folder contains components you added after installation, Salesforce prevents you from uninstalling the package.
    • When an installed letterhead is used for an email template you added after installation, Salesforce prevents you from uninstalling the package.
  • You can’t uninstall a package that removes all active business and person account record types. Activate at least one other business or person account record type, and try again.
  • You can’t uninstall a package if a background job is updating a field added by the package, such as an update to a roll-up summary field. Wait until the background job finishes, and try again.
  • Uninstall export files contain custom app data for your package, excluding some components, such as documents and formula field values.
  • For some package types, you can also uninstall them with the Salesforce command-line interface (CLI).