Application Installation Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
PDF

Newer Version Available

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

Installing Packages

Available in: Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions

User Permissions Needed
To install packages: “Download AppExchange packages”
To install a package from AppExchange, follow this procedure from the beginning. If you received an installation link, click the link and skip to the Enter the requested information step.

If the app is in a managed package, you cannot change some Salesforce components after you install them. For a list of editable components in a managed package, see the ISVforce User Guide. Managed packages also have a namespace prefix that is prepended to all uniquely named components, such as custom fields. For more information on namespace prefixes, see “Registering a Namespace Prefix” in the Salesforce online help.

Warning

Only one person in your organization can install or upload a package at a time.

Note

  1. Click the AppExchange link in your organization or go directly to www.appexchange.com.
  2. Browse the AppExchange site to find the application you want to install.
  3. Click Get It Now from the application information page.

    If the listing does not have a Get It Now option, it may be a partner app that you can download and use outside of Salesforce. Contact the publisher for more information.

  4. Select your environment type: production or sandbox (test).
  5. Enter the requested information. For production environments, enter your username and password, read the user terms, select the I have read and agree... checkbox, and click Install.

    For sandbox environments, complete the information in the form provided and click Submit. This package is removed from your sandbox organization whenever you create a new sandbox copy.

  6. If the package is password-protected, enter the password you received from the publisher.
  7. Review the package items and click Continue.
    If you’re installing an upgrade to a managed package, review the list of new items that the upgrade will add.

    Some package items, such as validation rules or record types, may not display in the Package Item list but are included in the package and install with the other items. If there are no items in the Package Items list, the package may contain only minor changes not recorded in the Package Items list.

    Note

  8. Review the API access that package components have been granted to ensure they are acceptable, and click Next if they are. If they are not, click Cancel. For more information, see “About API and Dynamic Apex Access in Packages” in the Salesforce online help.
  9. When installing unmanaged packages, you can select Resolve Naming Conflicts Automatically. When this is selected, Salesforce changes the name of the component in the package being installed.
  10. In Enterprise, Unlimited, Performance, and Developer Editions, choose a security option, and click Next:
    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
    • Record Type settings—determined by the package creator

    The Customer Portal User, Customer Portal Manager, High Volume Customer Portal, Authenticated Website, Partner User, and standard profiles receive no access.

    Note

    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.

    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.

    Note

  11. In Enterprise, Unlimited, Performance, and Developer Editions, if you chose Select security settings, select the level of access to give users in each profile and click Next. Standard options are:
    • 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.

  12. Click Install to install all the components in the package you have selected. See Configuring Installed Packages in the Salesforce online help to view the standard settings each type of component will have after you install.

    During installation, Salesforce automatically resolves any references to package components from the source organization. For example, if a custom link in the package refers to a document, the ID for the document will be different once you install it so Salesforce automatically alters the installed custom link to refer to the new ID in your organization. Salesforce also checks and verifies any 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. See Understanding Dependencies in the Salesforce online help for more information on package dependencies.

    When you install a component that contains an Apex script, 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 may fail. You can select to install regardless of unit test failures.

    For reasons Salesforce could prevent an install, see “Why did my installation or upgrade fail?” in the Salesforce online help.

    Note

  13. Click OK.
  14. Configure your package. See ”Configuring Installed Packages” in the Salesforce online help.
  15. 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.
  16. If you are reinstalling a package, see Importing Package Data in the Salesforce online help to reimport the package data using the export file you received after uninstalling.
  17. If you installed a managed package, click Manage Licenses, to assign licenses to users. See Managing Licenses for Installed Packages in the Salesforce online help.