Packaged components and org edition limits
Key Takeaway
Components from a managed package publicly listed on AppExchange don't count against your edition allocation, but they still count against the total limit for your org. Components from a package that isn't publicly listed count against your edition allocation, even if the package is managed.
When you install a package, its components are added to your org. All Salesforce editions limit the number of apps, objects, and tabs you can use, and components from installed packages can take up that room. Whether they use up your edition allocation depends on whether the package is managed and publicly listed on AppExchange. An app builder should check this before installing.
Which packages count against your edition allocation
Two separate limits apply to packaged components: your edition allocation and the total limit for your Salesforce org. The kind of package decides whether its components count against your edition allocation.
| Package | Do its custom objects, custom fields, tabs, and apps count against your edition allocation? |
|---|---|
| Managed package publicly listed on AppExchange | No |
| Managed package distributed without a public AppExchange listing | Yes |
| Unmanaged package not publicly listed on AppExchange | Yes |
Being managed is not enough to be exempt from your edition allocation. The package also has to be publicly listed on AppExchange.