Install Packages and Manage Apps. salesforce Salesforce Organization

Set Up and Maintain Your Salesforce Organization Install Packages and Manage Apps

Install Packages and Manage Apps

Installed Packages

You can install packages into your Salesforce organization, and then configure and manage them.

To view the packages you’ve installed, from Setup, enter “Installed” in the Quick Find box, and then select Installed Packages.

EDITIONS

Available in: both Salesforce

Classic and Lightning

Experience

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

Install a Package

Here are the steps for installing a package.

Pre-Installation Steps

1. In a browser, go to the installation URL provided by the package developer, or, if you’re installing a package from the AppExchange, click Get It Now from the application information page.

Note: If you’re installing into a sandbox, replace the www.salesforce.com portion of the installation link with test.salesforce.com. The package is removed from your sandbox organization whenever you create a new sandbox copy.

2. Enter your username and password for the Salesforce organization in which you want to install the package, and then click the login button.

3. If the package is password-protected, enter the password you received from the publisher.

4. Optionally, if you’re installing an unmanaged package, select

Rename conflicting components in package

. When you select this option, Salesforce changes the name of a component in the package if its name conflicts with an existing component name.

EDITIONS

Available in: both Salesforce

Classic and Lightning

Experience

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

To install packages:

•

“Download

AppExchange

Packages”

Default Installation

Click Install. You’ll see a message that describes the progress and a confirmation message after the installation is complete.

Custom Installation

Follow these steps if you need to modify the default settings as an administrator.

1. Choose one or more of these options, as appropriate.

696

Set Up and Maintain Your Salesforce Organization Installed Packages

•

Click View Components. You’ll see an overlay with a list of components in the package. For managed packages, the screen also contains a list of connected apps (trusted applications that are granted access to a user's Salesforce data after the user and the application are verified). Review the list to confirm that the components and any connected apps shown are acceptable, and then close the overlay.

Note: Some package items, such as validation rules, record types, or custom settings might not appear in the Package

Components list but are included in the package and installed with the other items. If there are no items in the Package

Components list, the package might contain only minor changes.

•

If the package contains a remote site setting, you must approve access to websites outside of Salesforce. The dialog box lists all the websites that the package communicates with. We recommend that a website uses SSL (secure sockets layer) for transmitting data. After you verify that the websites are safe, select Yes, grant access to these third-party websites and click Continue, or click Cancel to cancel the installation of the package.

Warning: By installing remote site settings, you’re allowing the package to transmit data to and from a third-party website.

Before using the package, contact the publisher to understand what data is transmitted and how it's used. If you have an internal security contact, ask the contact to review the application so that you understand its impact before use.

•

Click API Access. You’ll see an overlay with a list of the API access settings that package components have been granted. Review the settings to verify they’re acceptable, and then close the overlay to return to the installer screen.

•

In Enterprise, Performance, Unlimited, and Developer Editions, choose one of the following security options.

Note:

Depending on the type of installation, you might not see this option. For example, in Group and Professional

Editions, or if the package doesn’t contain a custom object, Salesforce skips this option, which gives all users full access.

Install for Admins Only

Specifies the following settings on the installing administrator’s profile and any profile with the "Customize Application" permission.

–

Object permissions—“Read,” “Create,” “Edit,” “Delete,” “View All,” and “Modify All” enabled

–

Field-level security—set to visible and editable for all fields

–

Apex classes—enabled

–

Visualforce pages—enabled

–

App settings—enabled

–

Tab settings—determined by the package creator

–

Page layout settings—determined by the package creator

–

Record Type settings—determined by the package creator

After installation, if you have Enterprise, Performance, Unlimited, or Developer Edition, set the appropriate user and object permissions on custom profiles as needed.

Install for All Users

Specifies the following settings on all internal custom profiles.

–

Object permissions—“Read,” “Create,” “Edit,” “Delete,” “View All,” and “Modify All” enabled

–

Field-level security—set to visible and editable for all fields

–

Apex classes—enabled

–

Visualforce pages—enabled

–

App settings—enabled

–

Tab settings—determined by the package creator

–

Page layout settings—determined by the package creator

697

Set Up and Maintain Your Salesforce Organization Installed Packages

–

Record Type settings—determined by the package creator

Note: The Customer Portal User, Customer Portal Manager, High Volume Customer Portal, Authenticated Website,

Partner User, and standard profiles receive no access.

Install for Specific Profiles...

Enables you to choose the usage access for all custom profiles in your organization. You can set each profile to have full access or no access for the new package and all its components.

–

Full Access—Specifies the following settings for each profile.

•

Object permissions—“Read,” “Create,” “Edit,” “Delete,” “View All,” and “Modify All” enabled

•

Field-level security—set to visible and editable for all fields

•

Apex classes—enabled

•

Visualforce pages—enabled

•

App settings—enabled

•

Tab settings—determined by the package creator

•

Page layout settings—determined by the package creator

•

Record Type settings—determined by the package creator

–

No Access—Specifies the same settings as Full Access, except all object permissions are disabled.

You might see other options if the publisher has included settings for custom profiles. You can incorporate the settings of the publisher’s custom profiles into your profiles without affecting your settings. Choose the name of the profile settings in the drop-down list next to the profile that you need to apply them to. The current settings in that profile remain intact.

Alternatively, click Set All next to an access level to give this setting to all user profiles.

2. Click Install. You’ll see a message that describes the progress and a confirmation message after the installation is complete.

•

During installation, Salesforce checks and verifies dependencies. An installer’s organization must meet all dependency requirements listed on the Show Dependencies page or else the installation will fail. For example, the installer's organization must have divisions enabled to install a package that references divisions.

•

When you install a component that contains Apex, all unit tests for your organization are run, including the unit tests contained in the new package. If a unit test relies on a component that is initially installed as inactive, such as a workflow rule, this unit test might fail. You can select to install regardless of unit test failures.

•

If your installation fails, see Why did my installation or upgrade fail?

on page 714.

Post-Installation Steps

If the package includes post-installation instructions, they’re displayed after the installation is completed. Review and follow the instructions provided. In addition, before you deploy the package to your users, make any necessary changes for your implementation. Depending on the contents of the package, you might need to perform some of the following customization steps.

•

If the package includes permission sets, assign the included permission sets to your users who need them. In managed packages, you can't make changes to permission sets that are included in the package, but subsequent upgrades happen automatically. If you clone a permission set that comes with a managed package or create your own, you can make changes to the permission set, but subsequent upgrades won't affect it.

•

If you’re re-installing a package and need to re-import the package data by using the export file that you received after uninstalling,

see Importing Package Data on page 707.

•

If you installed a managed package, click Manage Licenses to assign licenses to users.

698

Set Up and Maintain Your Salesforce Organization Installed Packages

Note: You can’t assign licenses in Lightning Experience. If you need to assign a license, switch to Salesforce Classic.

•

Configure components in the package as required. For more information, see Configuring Installed Packages

on page 699.

SEE ALSO:

Upgrading Packages

Installation Guide: Installing Apps from Force.com AppExchange

Installed Packages

Configuring Installed Packages

Many components have an Is Deployed attribute that controls whether they are available for end users. After installation, all components are immediately available if they were available in the developer's organization. Before making the package available to your users, make any necessary changes for your implementation. Depending on the contents of the package, you might need to customize the following items:

EDITIONS

Available in: Salesforce

Classic

Configure Option

If the publisher included a link to an external website with information about configuration,

AppExchange Downloads page displays a Configure option next to the package in Setup when you click Installed Packages. Click Configure to view the publisher's suggested configurations.

Available in:

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

Custom Fields and Custom Links

Add any necessary custom fields or links to the new custom objects.

Custom Object

Enable tracking on objects that aren't in this package, but that have fields that are tracked in

Chatter. For example, if you want to track a custom field on Account, you must make sure the

Account standard object is enabled for tracking.

USER PERMISSIONS

To install packages:

•

“Download

AppExchange

Packages”

Custom Report Types

If the

Report Type Name

of a custom report type matches one used within your organization, change the

Report Type Name confusion between the two report types.

after you install the package to avoid any

To configure installed packages:

•

“Customize Application”

Dashboard Running User

The

Running User

for any dashboards are set to the user installing the package. You can edit the properties of the dashboard and change the

Running User

to a user that has the security settings you want applied to the dashboard.

Folders

When apps contain documents, email templates, reports, or dashboards, Salesforce creates new folders in the installer’s organization using the publisher’s folder names. Make sure these folder names are unique in your organization.

All users can see new folders. Configure folder settings before you deploy if you want them to have limited visibility.

Home Page Layouts

Custom home page layouts included in the package are not assigned to any users. To make them available to your users, assign them to the appropriate profiles.

List Views

List views included in apps are visible to all users. Change the visibility of these list views if necessary.

699

Set Up and Maintain Your Salesforce Organization Installed Packages

Page Layouts

All users are assigned the default page layout for any custom objects included in the package. Administrators of Enterprise, Unlimited,

Performance, and Developer Edition organizations can configure the page layout for the appropriate users.

If a custom object in the package includes any relationships to standard objects, add them as related lists on the appropriate page layouts.

If the package includes any custom links, add them to the appropriate page layouts.

If your organization has advanced currency management enabled, currency roll-up summary fields are invalid if they are on accounts and summarizing opportunity values, or on opportunities and summarizing custom object values. Remove these fields from any page layouts.

Permission Sets

Assign permission sets included in a package to the users who need access to the package.

You can't edit permission sets that are included in a managed package. If you clone a permission set that comes with the package or create your own, you can make changes to the permission set, but subsequent upgrades won't affect it.

Translation Workbench

Translated values for installed package components are also installed for any language that the developer has included. Any package components the developer has customized within setup, such as a custom field or record type, display in the installer’s setup pages in the developer’s language (the language used when defining these components). Users in the installer’s organization automatically see translated values if their personal language is included in the package. Additionally, installers can activate additional languages as long as the Translation Workbench is enabled.

Workflow Alerts

If the recipient of a workflow alert is a user, Salesforce replaces that user with the user installing the package. You can change the recipients of any installed workflow alerts.

Workflow Field Updates

If a field update is designed to change a record owner field to a specific user, Salesforce replaces that user with the user installing the package. You can change the field value of any installed field updates.

Workflow Outbound Messages

Salesforce replaces the user in the

User to send as

field of an outbound message with the user installing the package. You can change this value after installation.

Workflow Rules

Workflow rules are installed without any time-based triggers that the developer might have created. Set up time-based triggers as necessary.

Workflow Tasks

Salesforce replaces the user in the

Assigned To

field with the user installing the package. You can change this value after installation.

Make any more customizations that are necessary for your implementation.

Note:

Anything you add to a custom app after installation will be removed with the custom app if you ever uninstall it.

SEE ALSO:

Installed Packages

Platform Encryption Considerations

700

Set Up and Maintain Your Salesforce Organization Uninstalling a Package

Uninstalling a Package

You can remove any installed package, including all of its components and all data in the package.

Additionally, 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

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, as well as any associated notes and 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 period of time after the uninstall completes.

EDITIONS

Available in: both Salesforce

Classic and Lightning

Experience

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

Tip: If you reinstall the package later and want to reimport the package data, see

Importing Package Data on page 707.

To uninstall packages:

•

“Download

AppExchange

Packages”

Notes on Uninstalling Packages

•

If you’re uninstalling a package that includes a custom object, all components on that custom object are also deleted. This includes custom fields, validation rules, s-controls, custom buttons and links, as well as workflow rules and approval processes.

•

You can’t uninstall a package whenever any component in the package is referenced by a component that will not get included in the uninstall. For example:

–

When an installed package includes any component on a standard object that another component references, Salesforce prevents you from uninstalling the package. This means that you can install a package that includes a custom user field and build 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, Salesforce prevents you from uninstalling the package. This means that you can 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 if a field added by the package is being updated by a background job, 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.

701

Set Up and Maintain Your Salesforce Organization Managing Package Installations

Managing Package Installations

View a list of the packages you installed from AppExchange and data export files from uninstalled packages by clicking Installed Packages. These packages can be either managed or unmanaged.

EDITIONS

Note:

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.”

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. 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 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.

Available in: both Salesforce

Classic and Lightning

Experience

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

•

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.

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”

•

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.

Note: If you have not installed a licensed managed package, the

Publisher

,

Status

,

Allowed Licenses

,

Used

Licenses

, and

Expiration Date

fields do not appear.

After an uninstall, Salesforce automatically creates an export file containing the package data, as well as any associated notes and 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 period of 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.

702

Set Up and Maintain Your Salesforce Organization Managing Package Installations

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.

SEE ALSO:

Displaying Installed Package Details

Importing Package Data

Displaying Installed Package Details

The package detail page displays essential details about the package you installed from AppExchange.

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 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.

•

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

Action

Allowed Licenses

Apps

Description

Can be one of two options:

• Uninstall

• Manage 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.

The number of custom apps in the package.

EDITIONS

Available in: both Salesforce

Classic and Lightning

Experience

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

To uninstall packages:

•

“Download

AppExchange

Packages”

To manage user licenses for an AppExchange package:

•

“Manage Package

Licenses”

703

Set Up and Maintain Your Salesforce Organization Managing Package Installations

Attribute

Connected Apps

Description

Expiration Date

Installed Date

Limits

Namespace

Objects

Package Name

Publisher

Status

Tabs

Used Licenses

Version Name

Description

A list of the connected apps that can have access to a user's

Salesforce data after the user and the application have been verified.

A detailed description of the package.

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 only displayed if the package is managed and licensed.

The date of the package installation.

If checked, the package’s custom apps, tabs, and objects count toward your organization’s limits.

The 1- to 15-character alphanumeric identifier that distinguishes a package and its contents from packages of other developers on

AppExchange.

The number of custom objects in the package.

The name of the package, given by the 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.

The state of a package. Available values include:

•

Trial

•

Active

•

Suspended

•

Expired

•

Free

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

The number of custom tabs in the package.

The total number of licenses that are already assigned to users.

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

The version name for this package version. The version name is the marketing name for a specific release of a package. It is more descriptive than the

Version Number

.

Viewing Installed Package Details

The installed package detail page lists the following package attributes (in alphabetical order):

704

Set Up and Maintain Your Salesforce Organization

Attribute

API Access

Apps

Description

First Installed Version Number

Installed By

Limits

Modified By

Namespace

Objects

Package Name

Package Type

Post Install Instructions

Publisher

Release Notes

Tabs

Version Name

Managing Package Installations

Description

The type of access that the API and dynamic Apex code that package components have. The default setting is Unrestricted, which means that all package components that access the API have the same access as the user who is logged in. Click Enable

Restrictions or Disable Restrictions to change the API and dynamic Apex access permissions for a package.

The number of custom apps in the package.

A detailed description of the package.

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 have installed. If you ever report an issue with a managed package, include the version number in this field when communicating with the publisher.

The name of the user that installed this package in your organization.

If checked, the package’s custom apps, tabs, and objects count toward your organization’s limits.

The name of the last user to modify this package, including the date and time.

The 1- to 15-character alphanumeric identifier that distinguishes a package and its contents from packages of other developers on

AppExchange.

The number of custom objects in the package.

The name of the package, given by the publisher.

Indicates whether the package is managed or unmanaged.

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.

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.

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.

The number of custom tabs in the package.

The version name for this package version. The version name is the marketing name for a specific release of a package. It is more descriptive than the

Version Number

.

705

Set Up and Maintain Your Salesforce Organization Managing Package Installations

Attribute

Version Number

Description

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 is no patchNumber

, it is 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.

The following component information is displayed (in alphabetical order):

Attribute

Action

Name

Parent Object

Type

Description

Can be one of two options:

• Undelete

• Delete

Displays the name of the component.

Displays the name of the parent object a component is associated with. For example, a custom object is the parent of a custom field.

Displays the type of the 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

Action

Name

Parent Object

Description

Can be one of two options:

• Undelete

• Delete

Displays the name of the component.

Displays the name of the parent object a component is associated with. For example, a custom object is the parent of a custom field.

706

Set Up and Maintain Your Salesforce Organization Managing Package Installations

Attribute

Type

Description

Displays the type of the component.

SEE ALSO:

Importing Package Data

Managing Package Installations

Importing Package Data

When you uninstall an AppExchange package, Salesforce automatically creates an export file containing the package data as well as any associated notes and attachments. If you choose to install the package again, you can import this data.

To import your AppExchange package data, use one of the following tools that is available for your

Edition:

•

For Group Edition, use the appropriate import wizard.

•

For Professional Edition, use the appropriate import wizard or any compatible Salesforce ISV

Partner integration tool.

•

For Enterprise, Developer, Performance, and Unlimited Edition, use the Data Loader.

Notes on Importing AppExchange Package Data

•

Salesforce converts date fields into date/time fields upon export. Convert the appropriate fields into date fields before you import.

•

Salesforce exports all date/time fields in Greenwich Mean Time (GMT). Before importing these fields, convert them to the appropriate time zone.

•

The value of auto number fields may be different when you import. To retain the old values, create a new custom auto number field on a custom object before importing the data.

•

Salesforce updates system fields such as

Created Date

and

Last Modified Date when you import. To retain the old values for these fields, contact Salesforce support.

•

Relationships are not included in the export file. Recreate any master-detail or lookup relationships after importing your data.

•

Record type IDs are exported but not the record type name.

•

Field history is not exported.

•

Recreate any customizations that you made to the package after installation.

SEE ALSO:

Displaying Installed Package Details

Managing Package Installations

EDITIONS

Available in: both Salesforce

Classic and Lightning

Experience

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

To import Force.com

AppExchange package data:

•

The permissions required to use the import tool you choose, such as the import wizard or Data Loader.

707

Set Up and Maintain Your Salesforce Organization Managing Licenses for Installed Packages

Managing Licenses for Installed Packages

When you install a licensed managed package in your organization from AppExchange, you purchase a certain number of licenses from the package developer or publisher. You can assign each license to a user within your organization. If you assign all available licenses, but would like to grant licenses to additional users, you can reassign a license or purchase more. To get more licenses, contact the publisher of the managed package.

Note: 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.

1. From Setup, enter

Installed Packages

in the

Quick Find

box, then select Installed

Packages.

2. Click Manage Licenses next to the package.

Note:

To assign licenses for a package, you must have access to the package and at least one available license.

•

To assign licenses to more users, click Add Users.

•

To remove a license from a user, click Remove next to the user's name. To remove licenses from multiple users, click Remove Multiple Users.

•

Click any column heading to sort the users in ascending order using the data in that column.

Click the heading again to sort in descending order.

•

If available, select fewer or more to view a shorter or longer display list.

EDITIONS

Available in: Salesforce

Classic

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

To manage licenses for a

AppExchange package:

•

“Manage Package

Licenses”

SEE ALSO:

Assigning Licenses for Managed Packages

Assigning Licenses for Installed Packages

Removing Licenses for Installed Packages

Responding to License Manager Requests

708

Set Up and Maintain Your Salesforce Organization Managing Licenses for Installed Packages

Assigning Licenses for Managed Packages

When you install a licensed managed package in your organization from AppExchange, you purchase a certain number of licenses from the package developer or publisher. You can assign each license to a user within your organization. If you assign all available licenses, but would like to grant licenses to additional users, you can reassign a license or purchase more. To get more licenses, contact the publisher of the managed package.

The Managed Packages related list on the user detail page lists all managed packages that user is assigned. Assigning a license for a managed package makes the package available to the user within

Salesforce.

Unmanaged packages will not appear on this list, as you cannot assign licenses for them.

To assign a user to a license for one of the available managed packages:

1. From Setup, enter

Users

in the

Quick Find

box, then select Users.

EDITIONS

Available in: Salesforce

Classic

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

2. Click Assign Licenses from the Managed Packages list.

USER PERMISSIONS

3. Select the package you want to assign to the user. All available managed packages are listed in the Unassigned Packages list. After selecting a package, Salesforce automatically moves it to the Selected Packages list.

To edit users:

•

“Manage Internal Users”

The Unassigned Packages list displays all packages that this user could access if assigned a license. Packages will not appear on this list if they are unmanaged, uninstalled, in use, or not available.

To manage licenses for an

AppExchange package:

•

“Manage Package

Licenses”

•

Click a letter to view the packages that begin with that letter or click All to display all available managed packages.

•

Click select shown to select all packages displayed in the Unassigned Packages list on the current page, adding them to the

Selected Packages list below.

•

Click deselect shown or deselect all to move packages from the Selected Packages area to the Unassigned Packages area.

4. Click Add.

To revoke a license from this user, click the

Remove

link next to the appropriate package name.

SEE ALSO:

Managing Licenses for Installed Packages

709

Set Up and Maintain Your Salesforce Organization Managing Licenses for Installed Packages

Assigning Licenses for Installed Packages

To assign licenses to Force.com AppExchange users:

Note: 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.

1. From Setup, enter

Installed Packages

in the

Quick Find

box, then select Installed

Packages to find the installed package that has available licenses.

2. Click the Manage Licenses link next to the package name.

3. Click Add Users.

4. Choose a view from the drop-down list, or click Create New View to build a new custom view.

5. Click a letter to filter the users with a last name that corresponds with that letter or click All to display all users who match the criteria of the current view.

6. Select users.

•

To select individual users, use the checkboxes. Selected users are listed in the Selected list.

When the list includes all users to which you want to assign licenses, click Add.

•

To select all users for the current view, click Add All Users then click OK.

Note:

You can also add a single user from the user's detail page.

EDITIONS

Available in: Salesforce

Classic

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

To manage licenses for an

AppExchange app:

•

“Manage Package

Licenses”

SEE ALSO:

Managing Licenses for Installed Packages

Removing Licenses for Installed Packages

To remove licenses for an AppExchange package from multiple users:

1. From Setup, enter

Installed Packages

in the

Quick Find

box, then select Installed

Packages.

2. Click Manage Licenses next to the package name.

3. Click Remove Multiple Users.

4. To show a filtered list of items, select a predefined list from the

View

drop-down list, or click

Create New View to define your own custom views.

5. Click a letter to filter the users with a last name that corresponds with that letter or click All to display all users who match the criteria of the current view.

6. Select users.

•

To select individual users, use the checkboxes. Selected users appear in the Selected for

Removal list. When the list includes all users for which you want to remove licenses, click

Remove.

•

To select all users in the current view, click Remove All Users, then click OK.

You can also remove licenses for an AppExchange package from a single user using the following options:

EDITIONS

Available in: Salesforce

Classic

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

To manage licenses for an

AppExchange package:

•

“Manage Package

Licenses”

710

Set Up and Maintain Your Salesforce Organization Managing Licenses for Installed Packages

1. From Setup, enter

Users

in the

Quick Find

box, then select Users and click Remove next to the package in the managed packages list.

2. From Setup, enter

Installed Packages

in the

Quick Find

box, then select Installed Packages. Then, click Manage

Licenses next to the package name, and click Remove next to the user.

SEE ALSO:

Managing Licenses for Installed Packages

Responding to License Manager Requests

A license manager is a Salesforce organization that tracks all Salesforce subscribers installing a particular AppExchange package. Salesforce administrators can choose to designate another organization as the license manager for one of their packages. The license manager does not need to be the same organization as the one from which the package is managed. To choose another organization as the license manager, all you need is an email address (not a Salesforce username).

If a Salesforce administrator selects to have a third-party license manager and enters your email address, you will receive a license management request in email.

To respond to a registration request:

1. Click the link in the license management request email. This displays the registration request in the requestor's Developer Edition organization.

2. Click Accept to complete the registration process. Alternatively, click Reject to decline the request and close the browser; this prevents you from using the link again.

Note: If you accept this request, you authorize Salesforce to automatically create records in your Salesforce organization to track information about this package. Choosing a license manager organization is permanent and cannot be changed.

3. Enter the username and password for the Salesforce organization you want to use to manage licenses for this package. A license manager can be any Salesforce organization that has installed the free License Management Application (LMA) from Force.com AppExchange.

4. Click Confirm.

SEE ALSO:

Managing Licenses for Installed Packages

EDITIONS

Available in: Salesforce

Classic

Available in: Developer

Edition

Package uploads and installs are available in

Group, Professional,

Enterprise, Performance,

Unlimited, and Developer

Editions

USER PERMISSIONS

To respond to registration requests:

•

“Customize Application”

711

Set Up and Maintain Your Salesforce Organization Upgrading Packages

Assigning Licenses Using the API

Administrators can use the API to assign or revoke licenses for any managed package installed in their organization. License information for a package is stored in two objects, PackageLicense and

UserPackageLicense, which were previously accessible only from the Manage Licenses page under

Setup. These are now accessible as standard objects, so an administrator can assign licenses to specific users via API calls. This makes managing package licenses in a subscriber organization faster and easier, especially for large-scale deployments.

For example, suppose an administrator installs an app for use by all 200 salespeople in the company.

Assigning a license to each salesperson from the UI is inefficient and time-consuming. Using the

API, the administrator can assign licenses to all salespeople, based on their profile, in one step.

Here are some common licensing tasks that administrators can use the API to do.

•

Determine the number of package licenses in use and available.

•

Verify if a specific user has a license for the package.

•

Get a list of all users who have a license for the package.

•

Assign a package license to a user or group of users.

•

Revoke a package license that was previously assigned to a user.

For details of the PackageLicense and UserPackageLicense objects and a code sample, see the

Object Reference for Salesforce and Force.com

.

EDITIONS

Available in: Salesforce

Classic

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

To manage licenses for an

AppExchange app:

•

“Manage Package

Licenses”

Upgrading Packages

Salesforce supports upgrades for managed packages only. Publishers can publish an upgrade for a managed package and notify installers that the new version is available. Installers of a managed package can then install the upgrade as follows:

1. Before you install an upgrade, determine if the app you installed was from a managed package.

Look for the Managed - Installed icon on the detail pages for each component and on the list of packages installed.

If the app you installed is not from a managed package, upgrades for it are not available.

2. Then, install the upgrade in the same way you would install any other package from the

AppExchange. If the publisher provided a link to the new version, follow the link to the package posting and install it in your organization. The first page of the install wizard lists the current version you have installed, the version you’re about to install, and a list of additional components included in the new version.

Notes on Upgrading Managed Packages

Consider the following when upgrading a managed package:

•

All existing custom objects that were previously deployed will still be deployed. Salesforce prompts you to deploy any new custom objects or previously undeployed custom objects.

•

Profile settings for components in a package are editable by the customer but not upgradeable by the package developer. If the developer makes changes to any profile settings after releasing the package, those changes won’t be included in an upgrade. Customers will need to manually update the profile settings after upgrading the package. In contrast, permission sets in a package

EDITIONS

Available in: Salesforce

Classic

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

USER PERMISSIONS

To upload packages:

•

“Upload AppExchange

Packages”

To install and uninstall packages:

•

“Download

AppExchange

Packages”

712

Set Up and Maintain Your Salesforce Organization Installing Packages FAQ are upgradeable by the developer, so any changes the developer makes will be reflected in the customer organization after upgrading the package.

•

If the developer chooses to add universally required custom fields, the fields will have default values.

•

Translation Workbench values for components that are “editable but not upgradeable” are excluded from upgrades.

•

If an installed package has

Restricted

API access, upgrades will be successful only if the upgraded version does not contain any s-controls. If s-controls are present in the upgraded version, you must change the currently installed package to

Unrestricted

API access.

•

When you upgrade a package, changes to the API access are ignored even if the developer specified them. This ensures that the administrator installing the upgrade has full control. Installers should carefully examine the changes in package access in each upgrade during installation and note all acceptable changes. Then, because those changes are ignored, the administrator should manually apply any acceptable changes after installing an upgrade.

SEE ALSO:

Force.com Quick Reference for Developing Packages

Installing Packages FAQ

•

Can I uninstall packages that I installed from AppExchange?

•

Why did my uninstall fail?

•

Who can use AppExchange?

•

Why did my installation or upgrade fail?

•

Can I customize AppExchange packages?

•

Who can use AppExchange packages?

•

How can I upgrade an installed package?

•

How secure are the components I install?

•

What happens to my namespace prefix when I install a package?

•

Can I reinstall an AppExchange package after uninstalling it?

•

When I install a package that’s listed on the AppExchange, do custom objects, tabs, and apps in that package count against the limits of my Salesforce Edition?

EDITIONS

Available in: Salesforce

Classic

Available in:

•

Group

•

Professional

•

Enterprise

•

Performance

•

Unlimited

•

Developer

Can I uninstall packages that I installed from AppExchange?

Yes. All your installed packages are listed in the Installed Packages page. You can remove any package by clicking the Uninstall link next to the package name.

SEE ALSO:

Uninstalling a Package

Importing Package Data

713

Set Up and Maintain Your Salesforce Organization Installing Packages FAQ

Why did my uninstall fail?

Salesforce prevents you from uninstalling a package if it causes any remaining components to malfunction.

SEE ALSO:

Uninstalling a Package

Who can use AppExchange?

Anyone can browse and test drive AppExchange listings. Salesforce administrators and users with the “Download AppExchange packages” permission can install AppExchange apps. To publish an app on the AppExchange, a user must have both “Create AppExchange packages” and “Upload AppExchange packages” permissions.

Why did my installation or upgrade fail?

An installation can fail for several reasons:

•

The package includes custom objects that will cause your organization to exceed its limit of custom objects.

•

The package includes custom tabs that will cause your organization to exceed its limit of custom tabs.

•

The developer of the package has uploaded a more recent version of the package and has deprecated the version associated with this installation URL. Contact the publisher of the package to get the most recent installation URL.

•

You’re trying to install an extension to a package, and you don't have the base package installed.

•

The package requires that certain components are enabled in your organization, or that required features are enabled in your edition.

•

The package contains Apex code and you are not authorized to run Apex in your organization.

•

The package you’re installing has a failing Apex test.

Can I customize AppExchange packages?

Yes, all packages are customizable. However, to ensure compatibility with future versions, some aspects of managed packages can't be changed.

For a list of components that are editable in a managed package, see ISVforce Guide .

Who can use AppExchange packages?

If you use an Enterprise, Unlimited, Performance, or Developer Edition organization, you can choose which user profiles have access to the package as part of the installation process. Packages installed in Professional and Group Edition organizations are installed with “Full

Access” to all user profiles. However, regardless of Edition, all custom objects are installed in “In Development” mode which hides them from all standard users. Users must have the “Customize Application” permission to view custom objects in “In Development” mode.

When you are ready to roll out the package to other users, change the custom object status to “Deployed.”

How can I upgrade an installed package?

Managed packages are completely upgradeable. Before installing a package, contact the publisher to determine if it’s managed.

714