View Installed Package Details
View key details about a package installed from AppExchange, such as the number of custom apps, tabs, and objects that it uses. You can also assign licenses to users, uninstall the package, and purchase the package.
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 uninstall packages: | Download AppExchange Packages |
| To manage licenses for an installed package: | Manage Package Licenses |
To access the package detail page, from Setup, enter Installed Packages in the Quick Find box, select Installed Packages, and then click the name of the package that you want to view.
From this page, 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. You can’t assign licenses in Lightning
Experience. If you need to assign a license, switch to Salesforce Classic.
Note If you purchased a site license or if the managed package isn’t 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. - Optionally, click View Dependencies and review a list of components that rely on other components, permissions, or preferences within the package.
Viewing Installed Packages
The installed package page lists the following package attributes (in alphabetical order):
| Attribute | Description |
|---|---|
| Action | Can be one of two options:
|
| Allowed Licenses | The total number of licenses you purchased for this package. The value is ”Unlimited” if you have a site license for this package. This field is only displayed if the package is managed and licensed. |
| Apps | The number of custom apps in the package. |
| Connected Apps | A list of the connected apps that can have access to a user's Salesforce data after the user and the app have been verified. |
| Description | A detailed description of the package. |
| Expiration Date | The date that this license expires, based on your terms and conditions. The expiration date is ”Does Not Expire” if the package never expires. This field is displayed only if the package is managed and licensed. |
| Installed Date | The date of the package installation. |
| Limits | If checked, the package’s custom apps, tabs, and objects count toward your organization’s limits. |
| Namespace | The 1- to 15-character alphanumeric identifier that distinguishes a package and its contents from packages of other developers on AppExchange. |
| Objects | The number of custom objects in the package. |
| Package Name | The name of the package, given by the publisher. |
| Publisher | The publisher of an AppExchange listing is the Salesforce user or organization that published the listing. This field is only displayed if the package is managed and licensed. |
| Status | The state of a package. Available values include:
This field is only displayed if the package is managed and licensed. |
| Tabs | The number of custom tabs in the package. |
| Used Licenses | The total number of licenses that are already assigned to users. This field is only displayed if the package is managed and licensed. |
| Version Name | The version name for this package version. The version name is the marketing name for a specific release of a package. It’s more descriptive than the Version Number. |
Viewing Package Details
The installed package detail page lists the following package attributes (in alphabetical order):
| Attribute | Description |
|---|---|
| Apps | The number of custom apps in the package. |
| Description | A detailed description of the package. |
| First Installed Version Number | The first installed version of the package in your organization. This field is only displayed for managed packages. You can reference this version and any subsequent package versions that you’ve installed. If you ever report an issue with a managed package, include the version number in this field when communicating with the publisher. |
| Installed By | The name of the user that installed this package in your organization. |
| Limits | If checked, the package’s custom apps, tabs, and objects count toward your organization’s limits. |
| Modified By | The name of the last user to modify this package, including the date and time. |
| Namespace | The 1- to 15-character alphanumeric identifier that distinguishes a package and its contents from packages of other developers on AppExchange. |
| Objects | The number of custom objects in the package. |
| Package Name | The name of the package, given by the publisher. |
| Package Type | Indicates whether the package is managed or unmanaged. |
| Post Install Instructions | A link to information on configuring the package after it’s installed. As a best practice, the link points to an external URL, so you can update the information independently of the package. |
| Publisher | The publisher of an AppExchange listing is the Salesforce user or organization that published the listing. This field is only displayed if the package is managed and licensed. |
| Release Notes | A link to release notes for the package. As a best practice, link to an external URL, so you can make the information available before the release and update it independently of the package. |
| Tabs | The number of custom tabs in the package. |
| Version Name | The version name for this package version. The version name is the marketing name for a specific release of a package. It’s more descriptive than the Version Number. |
| Version Number | The version number for the latest installed package version. The format is majorNumber.minorNumber.patchNumber, such as 2.1.3. The version number represents a release of a package. The Version Name is a more descriptive name for the release. The patchNumber is generated only when you create a patch. If there’s no patchNumber, it’s assumed to be zero (0). |
Unused Components
You can see a list of components deleted by the developer in the current version of the package. If this field is part of a managed package, it’s no longer in use and is safe to delete unless you’ve used it in custom integrations. Before deleting a custom field, you can keep a record of the data from Setup by entering Data Export in the Quick Find box, then selecting Data Export. After you've deleted an unused component, it appears in this list for 15 days. During that time, you can either undelete it to restore the field and all data stored in it, or delete the field permanently. When you undelete a field, some properties on the field are lost or changed. After 15 days, the field and its data are permanently deleted.
If you uninstall the package, any unused components are deleted.
The following component information is displayed (in alphabetical order):
| Attribute | Description |
|---|---|
| Action | Can be one of two options:
|
| Name | Displays the name of the component. |
| Parent Object | Displays the name of the parent object the component is associated with. For example, a custom object is the parent of a custom field. |
| Type | Displays the type of component. |
Package Components
You can see a list of the components included in the installed package. The following component information is displayed (in alphabetical order):
| Attribute | Description |
|---|---|
| Action | Can be one of two options:
|
| Name | Displays the name of the component. |
| Parent Object | Displays the name of the parent object the component is associated with. For example, a custom object is the parent of a custom field. |
| Type | Displays the type of component. |
