Set Up and Maintain Your Salesforce Organization Installed Packages
View a Mobile User’s Push Registration Information
With the Mobile Push Registrations Page, you can view any user's push registration information for general troubleshooting.
To view a user’s device push registration information:
1. From Setup, enter
Users
in the
Quick Find
box, then select Users.
2. Select a user.
3. On the user detail page next to
Mobile Push Registrations
, click View.
EDITIONS
Available in: Salesforce
Classic
Available in: All editions
USER PERMISSIONS
To view mobile push registration information:
•
“View Setup and
Configuration”
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, and Developer Editions
Install a Package
Install a managed or unmanaged package in your Salesforce org to add new functionality to your org. Choose a custom installation to modify the default package settings, including limiting access to the package. Before you install a package, verify on the AppExchange listing that the offering is compatible with your Salesforce edition.
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.
EDITIONS
Available in: both Salesforce
Classic and Lightning
Experience
Available in: Group,
Professional, Enterprise,
Performance, Unlimited, and Developer Editions
USER PERMISSIONS
To install packages:
•
“Download
AppExchange
Packages”
854
Set Up and Maintain Your Salesforce Organization Install a Package
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.
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.
•
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.
855
Set Up and Maintain Your Salesforce Organization Install a Package
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
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 872.
856
Set Up and Maintain Your Salesforce Organization Configuring Installed Packages
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 865.
•
If you installed a managed package, click Manage Licenses to assign licenses to users.
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 857.
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:
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.
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.
Custom Report Types
If the
Report Type Name
of a custom report type matches one used within your organization, change the
Report Type Name
after you install the package to avoid any confusion between the two report types.
EDITIONS
Available in: Salesforce
Classic
Available in: Professional,
Enterprise, Performance,
Unlimited, and Developer
Editions
USER PERMISSIONS
To install packages:
•
“Download
AppExchange
Packages”
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.
857
Set Up and Maintain Your Salesforce Organization Configuring Installed Packages
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.
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.
858
