Can't leverage permission sets capability in Professional Edition orgs
|Knowledge Article Number||000220361|
|Description||When trying to install the Apps or packages in Professional Edition (PE) orgs, installers are not prompted to set permissions for different profiles and access is provided for all the users by default. This is working as designed and PE permission set access was not provided as a means to allow vendors to circumvent this provided default access upon package installation.|
|Resolution||The purpose of allowing the creation of one permission set in PE orgs is provided for native use by customers and was not intended to be consumed or utilized by vendor's packages or apps. The package permissions on installing apps or packages into PE orgs has historically been "install for all users" by default.
Permission sets included in aloha packages are exempt from the 1 permission set limit in PE orgs but otherwise, customers may be unable to install a package which contains permission sets if one has already been created in the package installations target org and conversely, customer's may not be able to create a permission set if they've installed a managed package that includes a permission set.
However, we understand this concern/feature request from ISV partners, so it is recommended to create or promote changing this via an Idea Exchange post so that we may see this behavior altered with a future release.