Add-on
An Add-on in Salesforce is an additional product, feature, or capacity that can be purchased on top of a base Salesforce subscription.
Definition
An Add-on in Salesforce is an additional product, feature, or capacity that can be purchased on top of a base Salesforce subscription. Add-ons extend the functionality of your org beyond what is included in your standard license, such as additional storage, API calls, or premium features like Salesforce Shield.
In plain English
“Here's a simple way to think about it: an Add-on is anything you buy on top of your base Salesforce license. More storage. Salesforce Shield. Extra API calls. Industry-specific modules. Each is a separate purchase that extends what your edition includes.”
Worked example
Streamline Logistics has a Sales Cloud Enterprise license but needs advanced encryption and event monitoring. They purchase the Salesforce Shield add-on, which layers Platform Encryption, Event Monitoring, and Field Audit Trail onto their existing org. This gives them enterprise-grade security without switching to a different edition.
Why Add-ons are how Salesforce expands what your edition includes
A Salesforce edition (Enterprise, Unlimited, etc.) defines a baseline of features and capacity - a standard storage allocation, a default API call limit, the included objects, the standard set of products. Add-ons are how those baselines get extended. Need more storage? That's an add-on. Want Salesforce Shield encryption? Add-on. Higher API limits, additional Sandboxes, premium support, specific industry products - each is a discrete purchase that layers on top of your base license.
The reason this model matters past procurement is that the boundary between what's in your edition and what's behind an add-on can be invisible until you hit it. A new feature that everyone is excited about may turn out to require Sales Cloud Plus; a security control your team wants may live behind Shield. Knowing what your contract includes (and what it doesn't) is part of being a competent admin - and the add-on catalog evolves with each release, so this isn't a one-time review.
How organizations use Add-on
Procured Salesforce Shield as an add-on after a regulatory finding required encryption at rest - the add-on path was 3 weeks vs. 6 months for a custom alternative.
Added Health Cloud as an add-on to base Service Cloud rather than spinning up a separate org - preserved data continuity across patient touchpoints.
Bought additional API call capacity as integration volume grew, avoiding the throttling that would have broken nightly data syncs.
Trust & references
Hands-on resources to go deeper on Add-on.
Test your knowledge
Q1. What architecture concept is Add-on an example of?
Q2. What does Add-on represent in the Salesforce Platform?
Q3. How does Salesforce's multi-tenant model affect Add-on?
Discussion
Loading discussion…