Salesforce Foundations
Salesforce Foundations is a Setup feature that gives existing customers a curated set of capabilities from Sales, Service, Marketing, Commerce, and Data 360 (formerly Data Cloud) at no additional cost.
Definition
Salesforce Foundations is a Setup feature that gives existing customers a curated set of capabilities from Sales, Service, Marketing, Commerce, and Data 360 (formerly Data Cloud) at no additional cost. It is included with Enterprise, Unlimited, and Einstein 1 editions, and you turn it on from the Salesforce Foundations setup page rather than buying it separately.
The point of Foundations is to let a team that started on one cloud try a useful slice of the others without a new contract. A Sales org gets basic email campaigns and a storefront. A Service org gets unified profiles and AI agents. Salesforce adds capabilities to the package each release, so it is worth checking even if your org is already mature.
How Foundations packages cross-cloud capabilities
What you actually get in the box
Foundations bundles a working subset of five product areas, not full editions of each cloud. On the Sales side you get opportunity, account, contact, and lead management plus Email Builder Lite for batch sends and basic invoice generation. Service adds a Foundations Service Console, Knowledge for help articles, Omni-Channel routing, Email-to-Case threading, and Macros. Marketing covers campaigns, landing pages, forms, segments, and Flow-based automation, capped at up to 2,000 email sends per month. Commerce gives you a direct-to-consumer storefront with cart, checkout, search, SEO, and Pay Now payment links. Data 360 supplies unified customer profiles, segmentation, behavioral analysis, and consent management. Agentforce ties it together with prebuilt agents (Sales Coach, Sales Development, and a Service Agent), Prompt Builder, and a complimentary allotment of Flex Credits for running those agents. The mix is deliberately practical. It is meant to solve common gaps, like a Sales team that needs a newsletter or a Service team that wants one customer profile across channels, without dragging procurement into every small request.
Editions, eligibility, and what "no extra cost" means
Foundations is included at no additional charge with Enterprise, Unlimited, Einstein 1 Sales, and Einstein 1 Service editions. It also comes along when you buy Sales Cloud, Service Cloud, or many Industries products. There is no separate SKU to license and nothing to install from AppExchange. The phrase "no additional cost" is accurate, but it does not mean zero effort. The cost moves from your budget to your calendar, because every capability still needs configuration, permission assignment, and rollout planning. Some pieces also have their own ceilings or regional limits. The email cap of 2,000 sends per month is the obvious one. Pay Now is not available in every country (for example it is restricted in India, Brazil, and Japan at time of writing), and certain marketing features vary by region. Flex Credits for Agentforce are generous but finite, so heavy agent usage can exhaust them. Treat Foundations as a funded trial of adjacent clouds, not as an unlimited replacement for buying the full product when you outgrow the included scope.
Where it sits in the platform
Foundations is not a separate app. It is a Setup surface plus a set of permission set groups layered onto your existing org. You reach it through the Salesforce Foundations setup page, where you add products through Your Account and configure the key settings for each area. Enabling it also surfaces newer interface elements, including a personalized Home app, a vertical navigation bar, and dedicated Accounts and Contacts apps, along with Quick Settings for faster admin changes. Because everything runs inside your current org, the data lives next to your existing records and respects your sharing model. That is the real advantage over standing up a trial in a separate environment. A lead captured by a Foundations marketing form lands in the same database your sellers already work. An order from the Commerce storefront can feed Data 360, which can in turn power a confirmation email. The capabilities are curated, but they are first-class platform features, not a sandboxed demo.
A typical rollout, start to finish
Picture a Service Cloud org that wants light marketing and a storefront. The admin opens the Salesforce Foundations setup page and adds the products through Your Account. Next they enable the interface pieces, turning on Quick Settings, the vertical navigation bar, and the Home app so users see a consistent shell. Then they assign the standard permission set groups by role, giving service reps the Service group and a small marketing team access to the marketing features. For Marketing, they configure the sending email settings and grant app access, keeping the 2,000-send cap in mind when they plan campaign cadence. For Commerce, they assign users to the Commerce app and build the storefront. Data 360 is set up after the required products are added, then connected so profiles unify across the new touchpoints. The whole sequence is incremental. Each area can go live on its own schedule, which is exactly how you should approach it. Turning on all five at once tends to overwhelm both admins and end users and produces weak adoption.
Foundations versus the full clouds
It helps to be clear about what Foundations is not. It is not a way to get unlimited Marketing Cloud, full Commerce Cloud, or the complete Data 360 platform for free. The included features are intentionally scoped. Email Builder Lite is lighter than the full marketing email tooling. The storefront covers direct-to-consumer basics rather than every B2B commerce scenario. The email cap and Flex Credit allotment are real ceilings. When a team's needs grow past the included scope, the next step is buying the corresponding cloud or add-on, and Foundations makes that an easier internal sell because stakeholders have already seen the value. Think of it as the on-ramp. You prove a use case with the curated slice, measure adoption, then upgrade with evidence instead of a hypothesis. Foundations supplements your existing licenses. It does not replace understanding what each Cloud actually offers, and it does not remove the need to plan for the day you exceed the free tier.
Upgrade paths and migration notes
Customers do not all arrive at Foundations the same way. Some land on it by purchasing Enterprise or an Einstein 1 edition. Others migrate up from Salesforce Starter or Pro Suite, and that path has a useful guarantee. When you upgrade from Starter or Pro Suite, you keep your foundational Sales features and your previous permission set group assignments, so the move does not strip away what users already had. That continuity matters for change management, because nobody loses access on upgrade day. The practical takeaway is to plan migrations with the permission model in front of you. Map which groups your users currently hold, confirm which Foundations groups they should receive, and reconcile the two before you flip anything on. New capabilities arrive every release, so a quick review of the Foundations setup page each cycle is a cheap habit. You may find a feature your team has been asking to buy is now sitting in the package, already paid for, waiting only for you to configure it.
How to enable Salesforce Foundations
Foundations is enabled from a dedicated Setup page, then rolled out per area with permission set groups. Here is the high-level path an admin follows.
- Open the Foundations setup page
In Setup, go to the Salesforce Foundations setup page. Add the products you want through Your Account, which provisions the Sales, Service, Marketing, Commerce, and Data 360 capabilities into your org.
- Enable the interface and Home app
Turn on Quick Settings, the vertical navigation bar, and access to the Home app so users get a consistent shell. These changes apply across the org, so confirm they fit your existing navigation before enabling.
- Assign permission set groups by role
Distribute the standard permission set groups (such as General User and Service User) to the right people. Permissions, not just product provisioning, control who can see and use each Foundations feature.
- Configure each cloud area
Set up areas one at a time. Configure marketing email settings and grant app access, assign users to the Commerce app, and set up Data 360 after the required products are added so profiles unify across touchpoints.
Foundations marketing allows up to 2,000 email sends per month. Plan campaign cadence around this ceiling and upgrade to full marketing tooling when you need more volume.
Standard groups gate access by role. Decide group membership before enabling features so users see only what they should on day one.
Data 360 (formerly Data Cloud) must be configured after its required products are added. Set it up last so unified profiles can draw from the other enabled areas.
- "No additional cost" covers licensing, not effort. Every capability still needs configuration, permissions, and a rollout plan.
- Pay Now and some marketing features have regional limits (for example Pay Now is restricted in India, Brazil, and Japan), so confirm availability for your market.
- Enabling all five areas at once tends to swamp admins and users. Go live per capability on separate schedules for better adoption.
- Upgrading from Starter or Pro Suite keeps your foundational Sales features and previous permission set group assignments, so reconcile groups before you migrate.
Prefer this walkthrough as its own page? How to Salesforce Foundations in Salesforce, step by step
Trust & references
Cross-checked against the following references.
- Included Features in Salesforce FoundationsSalesforce
- Implement Salesforce FoundationsSalesforce
Straight from the source - Salesforce's reference material on Salesforce Foundations.
- Salesforce Foundations SetupSalesforce
- Discover Salesforce FoundationsSalesforce
Hands-on resources to go deeper on Salesforce Foundations.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What does Salesforce Foundations provide to existing Salesforce customers at no additional cost?
Q2. Where do admins primarily activate and manage Salesforce Foundations?
Q3. How does Salesforce Foundations help organizations work toward a more unified customer experience?
Discussion
Loading discussion…