Determine Which Users Can Access a Package
If you use an Enterprise, Unlimited, Performance, or Developer Edition organization, you can choose which users have access to the package.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Enterprise, Performance, Unlimited, and Developer Editions |
When installing a package you’re prompted to select which users can access the package. Your can choose from admins only, all users, or specific profiles. Review what package access is granted to each user type.
| Admins Only | All Users | Specific Profiles (Full Access) |
|---|---|---|
| Object permissions—Read, Create, Edit, Delete, View All Records, and Modify All Records enabled | Object permissions— Read, Create, Edit, and Delete enabled | Object permissions— Read, Create, Edit, and Delete enabled |
| Apex classes—enabled | Apex classes—enabled | Apex classes—enabled |
| Visualforce pages—enabled | Visualforce pages—enabled | Visualforce pages—enabled |
| App settings—enabled | App settings—enabled | App settings—enabled |
| Tab settings— access varies and is determined by the package developer | Tab settings— access varies and is determined by the package developer | Tab settings— access varies and is determined by the package developer |
| Page layout settings—access varies and is determined by the package developer | Page layout settings—access varies and is determined by the package developer | Page layout settings—varies based on package developer |
| Record Type settings—access varies and is determined by the package developer | Record Type settings—access varies and is determined by the package developer | Record Type settings—access varies and is determined by the package developer |
Packages installed in Professional and Group Edition organizations are installed with “Full Access” to all user profiles. However, regardless of Edition, all custom objects are installed in “In Development” mode, which hides them from all standard users. Users must have the “Customize Application” permission to view custom objects in “In Development” mode. When you’re ready to roll out the package to other users, change the custom object status to “Deployed.”
If the package developer has included settings for custom profiles, you can incorporate the settings of the publisher’s custom profiles into your profiles without affecting your settings. Choose the name of the profile settings in the dropdown list next to the profile that you’re applying them to. The current settings in that profile remain intact.
