Skip to content
Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full AppExchange Marketplace entry
How-to guide

How to install a solution from the AppExchange marketplace

Installing a solution from the marketplace is a guided flow that finishes inside Setup of the org you choose. Test in a sandbox or Developer Edition org first, then promote to production once the solution behaves as expected.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated Jun 16, 2026

Installing a solution from the marketplace is a guided flow that finishes inside Setup of the org you choose. Test in a sandbox or Developer Edition org first, then promote to production once the solution behaves as expected.

  1. Find and open the listing

    Browse or search appexchange.salesforce.com, open the solution's listing, and read the description, edition compatibility, and recent reviews. Confirm it supports your Salesforce edition before going further.

  2. Click Get It Now and pick a target org

    Select Get It Now, sign in, and use the account picker to choose a connected org. Choose Install in Sandbox for the first run rather than installing straight into production.

  3. Choose who gets access

    On the install screen, decide access: admins only, all users, or specific profiles. Admins-only is the safest default while you validate, since you can grant broader access through permission sets later.

  4. Validate, then promote to production

    Run a real workflow in the sandbox, check performance and any conflicts, then repeat Get It Now against production. Confirm the managed-package namespace appears under Installed Packages in Setup.

Install for Admins Onlyremember

Grants the package to System Administrators at install time; you assign other users access afterward via permission sets or profiles.

Install for All Usersremember

Grants access to every internal user immediately. Convenient for broadly used apps but riskier for a first install you have not validated.

Install for Specific Profilesremember

Lets you map each profile to a package access level, useful when only one team needs the solution.

Install in Sandbox vs Productionremember

The account picker target determines where the package lands. Salesforce recommends a sandbox or Developer Edition org first, then production.

Gotchas
  • Managed packages create a namespace that persists, so a misbehaving production-only install is hard to fully unwind. Validate in a sandbox first.
  • Edition and language filters exist for a reason. A package built for a higher edition may fail to install or silently lack features on a lower one.
  • A free listing still runs its own Apex. Evaluate free packages with the same care you give paid ones for performance and security impact.

See the full AppExchange Marketplace entry

AppExchange Marketplace includes the definition, worked example, deep dive, related terms, and a quiz.