Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Installed Packages entry
How-to guide

How to set up Installed Packages in Salesforce

Installed Packages is the Setup page listing every managed and unmanaged package installed in the org — AppExchange apps, Salesforce-published packages (CPQ, Field Service), custom internal packages. From here you check versions, configure package licenses, run package configuration wizards, and uninstall.

By Dipojjal Chakrabarti · Editor, Salesforce DictionaryLast updated Apr 20, 2026

Installed Packages is the Setup page listing every managed and unmanaged package installed in the org — AppExchange apps, Salesforce-published packages (CPQ, Field Service), custom internal packages. From here you check versions, configure package licenses, run package configuration wizards, and uninstall.

  1. Open Setup → Installed Packages

    Setup gear → Quick Find: Installed Packages → Installed Packages.

  2. Review the list

    Each row: Package Name, Publisher, Version, Action.

  3. Click Configure on a package for setup

    Many packages provide configuration wizards. Configure opens the package's Setup.

  4. Click Manage Licenses to assign / unassign user access

    Per-user package license management. Most managed packages need users to be licensed for the package.

  5. Click Upgrade when a new version is available

    Salesforce-published packages auto-show upgrade availability. Manually-uploaded unmanaged packages don't.

  6. Click Uninstall to remove a package

    Last resort. Uninstall removes all package metadata and data — irreversible without re-install + data import.

Key options
Configureremember

Package-specific setup.

Manage Licensesremember

User-level license assignment.

Upgraderemember

Move to a newer version.

Uninstallremember

Remove the package.

Gotchas
  • Uninstall is destructive. Removes all custom objects, fields, Apex, and DATA owned by the package. Always export package data before uninstalling.
  • Some packages have dependencies on other packages. Uninstalling the wrong one breaks dependent packages — read the dependency warning before confirming uninstall.
  • Manage Licenses requires the package's licensing model. Managed packages with site-license or named-user license need explicit assignment; without it, users can't access package functionality even if installed.

See the full Installed Packages entry

Installed Packages includes the definition, worked example, deep dive, related terms, and a quiz.