You are here:
Salesforce Professional Edition Allocations
Amounts for the Professional edition.
Required Editions
| Available in: Professional edition |
| Feature | Allocation | Notes |
|---|---|---|
| Active lookup filters | 5 per object | |
| Active validation rules per object | 20 | |
| Attachments: maximum size in the Notes & Attachments related list |
|
You can add an attachment to the Attachments related list of a case, solution, campaign, task, or event, or to the Notes & Attachments related list of an account, contact, lead, opportunity, or custom object. If you don’t see the related list on task or event page layouts, ask your admin to add it. |
| Content deliveries: default delivery bandwidth per rolling 24-hour window | 50 GB | |
| Content deliveries: default delivery view counts per rolling 24-hour window | 50,000 | |
| Content deliveries: maximum file size for online viewing | 25 MB | |
| Content: maximum file size |
|
|
| Content: maximum libraries | 2,000 | |
| Content: maximum number of documents | 30,000,000 | |
| Content: maximum number of documents and versions in a 24–hour period (adjustable) | 200,000 | |
| Content packs: maximum files | 50 | |
| Custom apps | 255 | To exceed this number, contact Salesforce. 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 | 100 | |
| Custom fields per object | 100 | 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 labels | 5,000 | |
| Custom links: maximum label length | 1,024 characters | |
| Custom links: maximum URL length | 3,000 bytes | When data is substituted for the tokens in the URL, the link can exceed 3,000 bytes. Some browsers enforce additional limits for the maximum URL length. |
| Custom objects | 50 | 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 objects: deletion of parent records in a many-to-many relationship | Available unless more than 200 junction object records are associated with the deleted parent record and the junction object has a roll-up summary field that rolls up to the other parent. | |
| Custom objects: maximum master-detail relationships | 2 | Each relationship is included in the maximum custom fields allowed. |
| Custom objects: maximum relationships (master-detail plus lookup) | 40 | |
| Custom profiles: maximum | 3 | |
| Divisions: maximum | 100 | |
| Documents: maximum size of custom app logo | 20 KB | |
| Documents: maximum size of document to upload | 5 MB | |
| Documents: maximum size of file name (with extension) | 255 characters | |
| Entitlement processes and milestones | You can create up to 1,000 entitlement processes total, with up to 10 milestones per process. | If your org was created before Summer ’13, its maximum entitlement processes can be lower. Contact Salesforce to increase it. |
| Field history tracking: maximum standard or custom fields tracked for standard or custom objects | 20 | |
| Flows and Processes: total | 5 | |
| Flows and Processes: active | 5 | |
| File size: maximum in Chatter and on the Files tab | 2 GB | |
| Fiscal years: maximum custom | 250 | |
| Formulas: maximum displayed characters after an evaluation of a formula expression | 1,300 | |
| Formulas: maximum length | 3,900 characters | |
| Formulas: maximum size when compiled | 5,000 bytes | |
| Formulas: maximum size when saved | 4,000 bytes | |
| Formulas: unique relationships per object | 15 | |
| Formulas: VLOOKUP functions per object | 10 | |
| Ideas: maximum size of HTML idea comment | 4 KB | |
| Ideas: maximum size of HTML idea description | 32 KB | |
| Lightning Apps | 10 | 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. |
| Lightning pages: maximum components in a region | 100 | |
| Master-detail relationship: maximum child records | 10,000 | |
| Objects: maximum number of deleting combined objects and child records | 100,000 | |
| Omni-Channel: maximum pending routing requests | Standard Omni-Channel: 200,000 / Enhanced Omni-Channel: 300,000 | Maximum objects that can be pending for Omni-Channel routing in an org. When an item is assigned to Omni-Channel-enabled queues, Omni attempts to route it to an available agent. If no agent is available, the work is pending routing. You may experience degraded performance in Omni-Channel Supervisor when queues surpass 10,000 pending routing requests. |
| Omni-Channel: maximum queued work items | 45,000 per hour | Maximum records that can be queued per hour in an org, across all Omni-Channel-enabled queues. Each time an item is assigned to an Omni-Channel queue, the platform checks how many items were queued in the preceding hour. If the max has been reached, the item isn’t assigned to the queue. |
| Permission sets: maximum (created) | 10 | |
| Permission sets: maximum (created and added as part of an installed managed AppExchange package) | 1,500 | |
| Permission set groups: maximum (created per org) | 10 | |
Permission sets groups: maximum (created and added as part of an installed managed AppExchange package) |
1,000 | |
| Quote PDF: maximum logo height | 150 pixels | |
| Quote PDF: maximum logo size | 5 MB | |
| Shared Activities | You can relate up to 50 contacts to nonrecurring tasks, nongroup tasks, and nonrecurring events. You can assign one primary contact. All others are secondary contacts. | |
| Sharing rules | You can create up to 300 sharing rules per object, including up to 50 criteria-based rules. | |
| Static resources | A static resource can be up to 5 MB. An org can have up to 250 MB of static resources total. | |
| Tabs | 1,210 | To exceed this number, contact Salesforce. 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. |
| Tags | A user is allowed a maximum of 500 unique personal tags and 5,000 instances of personal tags applied to records. Across all users, your org can have a maximum of 1,000 unique public tags, 50,000 instances of public tags applied to records, and 5,000,000 instances of personal and public tags applied to records. | |
| Users: maximum create | Unlimited | |
| Users: maximum created (Chatter Free) | 5,000 | |
| Web-to-Case: maximum new cases generated in a 24–hour period | 5,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 | 500 |
Did this article solve your issue?
Let us know so we can improve!
