Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 36 ยท CRM and Platform Concepts

Multitenancy, Editions and Platform Limits

Understand how Salesforce shares infrastructure between customers, how editions, licenses and storage limits shape what you can build, and what governor limits mean.

Salesforce runs millions of users for thousands of companies on shared infrastructure. That design explains many rules an admin must live with: limits on storage, on API calls, on how much a single automation can do, and on which features your edition includes. This lesson gives you the mental model so those limits stop being surprises.

Multitenancy

Multitenancy means many customers (tenants) share the same software and servers, but each sees only its own data. Think of an apartment building: shared plumbing and electricity, private apartments. Salesforce stores every org's data in shared databases, separated by an org identifier, and runs the same code for everyone.

Benefits for you:

  • Upgrades happen for everyone at once. No installing, no migrating servers.
  • Lower cost, because infrastructure is shared.
  • Same features and APIs for every org of a given edition.

The price is that one tenant must not be able to slow down the others. Salesforce therefore enforces strict limits.

Metadata-driven platform

Your objects, fields and layouts are not new database tables created by hand. They are metadata rows that the platform interprets at runtime. This is why you can add a custom field in seconds and why it appears in reports, APIs and layouts automatically.

Editions

An edition is a package of features, limits and price. For Sales and Service Cloud the common ones are:

Edition Typical audience Notes
Starter Very small teams Simplified setup, limited customization
Pro Suite Small teams Basic Sales and Service
Professional Small to mid-size Core CRM, limited customization and automation
Enterprise Mid-size and large Strong customization, more automation, sandboxes, more limits
Unlimited Large Enterprise features with higher allowances and premier support
Developer Practice and building Free, Enterprise-like features, small data limits

Availability and packaging change, so check Salesforce's current pricing page. What matters to an admin is that features such as Flow, record types, sandboxes, custom profiles and API access depend on the edition. If a Setup page is missing, the edition is a first suspect.

Licenses and permission set licenses

Editions give the org its features; user licenses decide what an individual can do.

  • Salesforce license: full access to standard CRM objects and custom apps (the usual license for employees).
  • Salesforce Platform license: access to custom objects and a few standard ones, cheaper, for people who only use custom apps.
  • Customer or partner community licenses: for external users in portals.
  • Chatter Free / Chatter External: collaboration only.
  • Feature licenses: Marketing User, Service Cloud User and so on, toggled on the user record.
  • Permission set licenses: unlock extra features that a permission set can then grant.

You can see how many licenses are used in Setup > Company Information. Hitting the limit means you must free one (deactivate a leaver) or buy more.

Storage limits

Orgs have two main storage pools:

  • Data storage: records. Most records count as about 2 KB each, regardless of how many fields are filled in, with some exceptions (for example, big text fields have limited effect, and a few objects count differently).
  • File storage: attachments, files and documents.

Both depend on edition and number of user licenses. Find them in Setup > Storage Usage. A common admin job is deleting stale data and archiving old attachments.

Python Stand-in: estimate data storage

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The estimate shows why activity-heavy objects such as Task and Case consume storage fastest.

Governor limits

Because tenants share servers, Salesforce caps what one transaction may consume. These are governor limits. They apply mainly to code (Apex) but also to flows, since flows run on the same engine. Some well-known examples for a synchronous transaction:

  • 100 SOQL (database) queries
  • 150 DML statements (inserts, updates and so on)
  • 10 seconds of CPU time
  • 6 MB heap size
  • 10,000 records can be processed by DML in one transaction

Flows are subject to these same limits. Beyond transaction limits there are org limits, such as a daily cap on API calls (depends on edition and licenses) and on scheduled emails.

Why this matters for an admin: a flow that runs a query inside a loop can hit the 100-query cap when someone loads 200 records at once. The cure is design: query once, loop over the results in memory.

Python Stand-in: why queries inside a loop hit limits

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The same principle, "bulkify your automation", is the most important performance rule on the platform.

Other limits you will meet

  • Custom objects, fields per object and relationship counts depend on edition (for example Enterprise allows many hundreds of custom fields per object, but each edition has a cap).
  • Report rows: a report displays up to a set number of rows (a few thousand) in the UI; exports and API retrieve more.
  • Email: single email sends per day are limited per org.
  • File size: a file upload has a per-file size cap.
  • Login attempts, session timeouts, API request rate.

Do not memorize the numbers. Learn where to look: the Limits link in an object's Object Manager page, System Overview in Setup, and Salesforce's official limits documentation.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does multitenancy mean?

    Tenants share software and servers, but each org's data is isolated.
  2. 2. Why does Salesforce enforce governor limits?

    Limits protect the shared platform and keep performance fair for everyone.
  3. 3. A flow runs a query for every record in a loop and fails when 200 records are saved. What is the likely cause?

    Queries inside loops multiply and exceed the per-transaction query limit; query once outside the loop instead.
  4. 4. Where would you check how much data storage your org has used?

    Storage Usage lists data and file storage and which objects consume it.

Summary

  • Multitenancy shares infrastructure between orgs; metadata describes each org's configuration.
  • The edition decides the features and limits; user licenses decide what each person can use.
  • Data and file storage are limited; governor limits cap what one transaction can do.
  • Design automation to handle many records at once and learn where to look up current limits.

Next: Leads, Accounts, Contacts and Opportunities