📢 Attention Salesforce Certified Trailblazers! Maintain your credentials and link your Trailhead and Webassessor accounts by April 19th. Learn more.
close

Learn About Org Design-Time Limits

Learning Objectives

After completing this unit, you’ll be able to:
  • Describe org design-time limits.
  • Identify the key org design-time limits.
  • Avoid org design-time limits.

What Are Org Design-Time Limits?

Let’s look at org design-time limits and allocations. As you’re customizing your org and determining all of the wonderful apps you want to build, note these design-time limits and allocations, which apply to your org as a whole.

Salesforce General Organization Limits

These limits apply to all orgs. They represent the level that we can support for all of our orgs combined, and in some cases they are physical limitations of our cloud infrastructure.

Think of these as the general guidelines that everyone has to consider when customizing orgs. If we think of phones as an analogy for orgs, the bandwidth (4G LTE, 3G, Edge) is an example of the general limits. No matter what model of phone you purchase, you have the same cellular band.

Salesforce Edition Allocations

These limits are applicable to the specific edition you purchase—Professional, Enterprise, Unlimited, and so on. And, of course, the limits change based on the edition level you purchase. If we think of phones as an analogy for orgs, the storage on the phone is an example of the edition limits. You can choose to purchase a phone that has larger storage

Returning to our navigation theme, org design-time limits are more globalized, like the weather or street lighting. Weather is a general limit. You can plan for it, but you can’t control it. Street lighting is more like an edition limit. You get light from above automatically, but you can improve your lighting along the way with a flashlight or headlight. Or you can change your route to avoid dark alleys.

A map view of a main route and an alternate route

More About General Limits

General limits ensure that all orgs can run effectively at the same time. These limits protect the shared resources so that no one org can hog all of them. They include the following.

The Number of Roles or Territories
Every time you create a new record, the system has to determine the sharing and visibility behind that record. As you increase the complexity of the role and territory tree, Salesforce has to evaluate the visibility for all of the nodes in the tree. As this tree gets larger, performance steadily suffers. After extensive testing, our performance engineers have set the limit to maintain reasonable performance for every org.
Number of Permission Sets
Permission sets, similar to roles and territories, have a limit to manage processing time. As you create more permission sets, your org’s processing uses a lot of system resources.
Joined Report Types
As you create more joined report types, your org’s processing can also begin to consume too many system resources.
Number of Global Picklists
As each of these picklists is referenced in the system, we have to load them into our caching layer. What does this mean? At Salesforce, we keep the global lists available in cached memory, rather than on disk. When you reference the global picklist, we can quickly find the info without performing a database request. This provides a better response for your users. If we allowed more global picklists per org, we could run out of room, and that means more uncached lists, and performance suffers.

Other key org limits include:

  • Custom permissions limits
  • Content libraries limits
  • Number of divisions
  • Number of email templates
  • Chatter groups in your org
  • External objects
  • Certificates
  • Tags

You can find details about these limits in the Salesforce Help. Typically, they are listed in a topic for their associated feature.

More About Edition Allocations

Salesforce delivers different levels of allocations depending on the edition. This way, customers have a number of options for choosing the edition that best fits their budget and expectations. Examples of edition allocations include:

  • The number of objects allowed per org
  • The number of dynamic dashboards and dashboard refreshes per hour
  • The maximum number of territory models
  • The number of sandboxes for testing

Explore your edition options. You can find them listed in the Salesforce Features and Edition Allocations.

Add-Ons

A few key features are set as defaults, and customers can opt to extend them. These add-ons let you customize some of your key allocations.

Salesforce Storage
While storage itself can seem inexpensive, it is the key part of all of Salesforce. Not only do we save your data, but we also back it up, manage it, and continually improve performance by upgrading our servers and storage. You can add storage in blocks of 1 GB.
User Licenses
Every org has a certain number of users who can log in to the system. To make sure you have enough user licenses, you can always purchase more.

Adding licenses does affect other limits, such as the daily API-request limit. The more licenses you have, the higher your daily allocation.

Additional Daily Calls
Even without purchasing additional user licenses or upgrading your edition, you can purchase certain features as add-ons, such as daily API calls and daily platform events.

Right-Size Your Edition

Avoiding these allocation maximums is really a matter of carefully planning your org and anticipating growth. It is always best to purchase the edition that fits most of your needs, budget, and planned growth. You can always upgrade your edition or purchase add-ons later.

An arrow hits the target
retargeting