Installed Packages is the page for ongoing package management. Most operations (install, upgrade, uninstall, license assign) are click-through; the deeper audit work involves reading package contents and dependency graphs.
- View the installed inventory
Setup, Quick Find, Installed Packages. The list shows every package with name, publisher, version, install date, and license status. Click any package name to see contents.
- Manage licenses
On a paid package, click Manage Licenses. Assign or revoke seats from the user list. Watch the Used vs Allocated ratio; over-allocation is a renewal conversation, under-allocation may indicate the package is not being used and the renewal can shrink.
- Configure post-install setup
Most packages have a Configure link that opens a publisher-specific setup wizard. Run this after first install. Configure links may include OAuth grants, API key entry, custom object initialization. Skipping this is the most common reason "the package isn''t working" tickets.
- Upgrade to a newer version
When the publisher releases a new version, Upgrade Available appears on the package row. Click Upgrade to install. Read the publisher''s release notes first; major-version upgrades may require post-upgrade reconfiguration.
- Uninstall when no longer needed
Click Uninstall. The wizard offers to export data first (CSV download per object). Confirm and execute. Test in sandbox before production uninstalls; some packages have hidden dependencies on other features.
Managed (namespaced, publisher-protected), Unmanaged (open code, customer-editable), Unlocked (modern DX format for internal teams).
Push (publisher auto-upgrades per org policy) or Pull (customer explicitly installs upgrades). Security patches typically push; major features pull.
Per-seat license (assign specific users) or org-wide license (all users covered). Per-seat is more common for paid AppExchange products.
Optional one-time CSV download per object before removal. Skip only when the package data is irrelevant or already exported elsewhere.
- Uninstalling without data export is permanent. Always export first unless the data is truly disposable.
- Managed packages cannot roll back to a prior version after upgrade. Test upgrades in sandbox; commitment is one-way.
- License over-allocation is a renewal-cycle problem, not a platform-enforced block. Track Used vs Allocated to avoid surprise true-up bills.
- Package dependencies prevent uninstall of base packages while extensions exist. Uninstall extensions first, then the base.
- Trial packages become read-only past expiration. Convert to paid before the trial ends or operational data freezes.