In an effort to be customer focused and make it as easy as possible on Salesforce Administrators, we want to provide permission sets with our package. However, standard object and custom objects that are children of standand objects in a master-detail record cannot be packaged. There are ideas out there, some have been open for several years.

We tried a different approach. As part of a post-install script, we attempted to create new permission sets with the the non-packagable permissions. These permission sets would not be part of our package, but administrators could easily assign these additional permission sets with the permission sets included in our package to make the setup process as easy as possible.

However, the post install user does not have permission to create permission sets. As an alternative to making standard objects and custom object children packagable in permission sets, allow the post-install script user to create permission sets.

According to me and as per my Implementation we can Create Permission Set using Post Install Script.
To avoid the confusion you can post your code snippets to get more comments/clearity so that others would get to know what you exactly doing with your code.

Salesforce

Need Help?

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.

Merge this idea with:

Optional Comments:

Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.

Details:

Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.