AppExchange is Salesforce's marketplace where administrators can find and install applications, components, and solutions to extend their org's functionality. When you install something from AppExchange, it arrives as a package, which is a bundle of related components such as objects, fields, apps,…AppExchange is Salesforce's marketplace where administrators can find and install applications, components, and solutions to extend their org's functionality. When you install something from AppExchange, it arrives as a package, which is a bundle of related components such as objects, fields, apps, and code. There are two main types of packages: managed and unmanaged.
Managed packages are typically created by Salesforce partners and independent software vendors (ISVs) who want to distribute and sell their applications while protecting their intellectual property. The components inside a managed package are locked, meaning administrators cannot modify the underlying code or certain metadata. This ensures the app behaves consistently across all orgs. A key advantage of managed packages is that they support seamless upgrades. The developer can push out new versions, and installed orgs receive updates while preserving customizations layered on top. Managed packages also do not count against your org's custom object and field limits, which is helpful for staying within governor thresholds. They are ideal for commercial, supported applications.
Unmanaged packages, by contrast, are used mainly for sharing open-source templates, sample code, or one-time distributions. Once installed, all components become fully editable, and administrators can view and change the source code as needed. However, unmanaged packages do not support upgrades. If the creator releases a newer version, you must install it separately and reconcile changes yourself. These components also count toward your org's limits. Unmanaged packages are best when you want a starting point that you intend to modify heavily.
As an administrator, understanding this distinction helps you make informed decisions about which solutions to adopt. Consider factors like whether you need ongoing support, upgrade paths, editability, and how the package affects your org limits. Choosing the right package type improves productivity, supports collaboration, and keeps your Salesforce environment maintainable and scalable over the long term.
AppExchange Apps: Managed vs Unmanaged Packages
Introduction AppExchange is Salesforce's marketplace for apps, components, and solutions that extend the functionality of your Salesforce org. Understanding the difference between managed and unmanaged packages is essential for any Salesforce Administrator, as it affects how you install, upgrade, and maintain solutions in your environment.
Why It Is Important Knowing the distinction between package types helps you make informed decisions when installing apps from AppExchange. It influences whether you can edit components, receive automatic updates, and how much control you retain over the installed solution. This knowledge is frequently tested in Salesforce certification exams and is critical for real-world administration.
What Is a Package? A package is a container that bundles together apps, components, and metadata (such as objects, fields, Apex code, and Visualforce pages) into a single unit. This makes it easy to share and deploy functionality across Salesforce orgs. There are two main types: managed and unmanaged.
Managed Packages A managed package is typically created by Salesforce partners and independent software vendors (ISVs) who want to distribute and sell their apps. Key characteristics include: - The components are locked, meaning subscribers cannot edit the underlying code or metadata. - The publisher can push upgrades and new versions to subscribers seamlessly. - Intellectual property is protected because the source code stays hidden. - Components use a namespace prefix to prevent naming conflicts with existing org components. - Ideal for commercial apps that require ongoing support and versioning.
Unmanaged Packages An unmanaged package is generally used for sharing open-source applications, templates, or one-time deployments. Key characteristics include: - The components are fully editable once installed in the target org. - There is no upgrade path; the publisher cannot push updates. - The source code is visible and modifiable by the subscriber. - No namespace prefix is applied to the components. - Best suited for distributing sample code or building blocks that developers will customize.
How It Works When you browse AppExchange and choose to install an app, Salesforce presents an installation wizard. During this process, you select who can access the package (admins only, all users, or specific profiles). Managed packages install as a self-contained unit that stays under publisher control, while unmanaged packages become part of your org and lose their connection to the original source once installed.
For managed packages, when the publisher releases a new version, you can upgrade with minimal effort while retaining your configurations. For unmanaged packages, any changes you want must be made manually since no upgrade mechanism exists.
How to Answer Exam Questions Exam questions often present a scenario and ask which package type is appropriate. Focus on these decision points: - If the question mentions upgradability or vendor-supported apps, the answer is usually managed packages. - If the question mentions editable components, open-source code, or no upgrade path, the answer points to unmanaged packages. - Remember that managed packages protect intellectual property and use namespaces. - Recall that unmanaged packages are typically for templates and one-time distributions.
Exam Tips: Answering Questions on AppExchange Apps: Managed vs Unmanaged Packages - Read each scenario carefully and identify keywords such as upgrade, editable, locked, or namespace. - When a business needs ongoing updates from a vendor, choose managed packages. - When a solution must be customized freely after installation, choose unmanaged packages. - Eliminate answer options that contradict the core traits of each package type. - Watch for questions about intellectual property protection, which always relates to managed packages. - Remember that only managed packages can be upgraded by the publisher. - Practice with sample scenarios so you can quickly match features to the correct package type during the exam.
