| Available in: Starter edition |
| FEATURE | ALLOCATION | NOTES |
|---|---|---|
| Active validation rules per object | 20 | |
| Custom apps | 0 | Lightning apps, custom apps, and custom tabs that are contained in a managed package that’s publicly posted on AppExchange don’t count against the allocations for your Salesforce edition. |
| Custom big objects | 10 | |
| Custom fields per object | 25 |
An org can’t have more than 900 custom fields on most object types, regardless of the edition or source of those fields. In addition to the limits listed above, you can install custom fields from AppExchange for a total of 900 fields. For example, you can create 800 custom fields on an object in the Unlimited Edition, plus install 100 custom fields from a managed package that are limited to specific objects. Additional restrictions apply for activities, long text area fields, relationship fields, and roll-up summary fields. For custom compound fields, each component counts as one custom field toward your org’s allocations. Each geolocation field counts as three custom fields: one for latitude, one for longitude, and one for internal use. Similarly, each custom address field counts as nine custom fields: one each for street, city, postal code, country code, state code, geocode accuracy level, longitude, and latitude, plus one for internal use. Additional restrictions apply for activities, long text area fields, relationship fields, and roll-up summary fields. See Custom Fields Allowed Per Object. |
| Custom objects | 0 |
The custom objects that are contained in a managed package that’s publicly posted on AppExchange don’t count against the allocations for your Salesforce edition. At the same time, an org can’t have more than 3,000 custom objects, regardless of the source or namespace of those objects. For example, in Unlimited Edition: 2,000 custom objects created, 1,000 custom objects installed by packages. Soft-deleted custom objects and their data count against your limits. We recommend that you hard delete or erase custom objects you no longer need. For usage restrictions that apply to Sales Cloud, Service Cloud, and Sales & Service Cloud, see this document. |
| Custom tabs | 0 | Lightning apps, custom apps, and custom tabs that are contained in a managed package that’s publicly posted on AppExchange don’t count against the allocations for your Salesforce edition. |
| Field history tracking: maximum standard or custom fields tracked for standard or custom objects | 20 | |
| Users: maximum create | Unlimited | |
| Users: maximum created (Chatter Free) | 5,000 | |
| Web-to-Case: maximum new cases generated in a 24–hour period | 55,000 | If your org exceeds its daily Web-to-Case or Web-to-Lead amount, the default case owner or default lead creator receives a notification email that contains information about the case or lead. When your org reaches the 24-hour max, Salesforce stores additional requests in a pending request queue that contains Web-to-Case and Web-to-Lead requests. The requests are submitted when the amount refreshes. The pending request queue has an allocation of 50,000 combined requests. If your org reaches the pending request maximum, additional requests are rejected and not queued. Your admin receives email notifications for the first five rejected submissions. Contact Salesforce Customer Support to change your org’s pending request allocation. |
| Web-to-Lead: maximum new leads generated in a 24–hour period | 55,000 |