function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
MJ Kahn / OpFocusMJ Kahn / OpFocus 

Field-Level Security Defined in Permission Sets in Managed Packages

I have a managed package that includes a Permission Set in which I've granted Read and Write access to all of the standard Lead fields. However, when I install the package into an org and then view the Permission Set, some (but not all) of the fields' Read and Write access checkboxes are unchecked. Why? 
Best Answer chosen by MJ Kahn / OpFocus
Vinita_SFDCVinita_SFDC
Hello,

You can not include standard object permission. Also, you can’t include object permissions for a custom object in a master-detail relationship where the master is a standard object.

Please refer: https://help.salesforce.com/HTViewHelpDoc?id=distribution_perm_sets_profile_settings.htm&language=en_US

All Answers

Vinita_SFDCVinita_SFDC
Hello,

You can not include standard object permission. Also, you can’t include object permissions for a custom object in a master-detail relationship where the master is a standard object.

Please refer: https://help.salesforce.com/HTViewHelpDoc?id=distribution_perm_sets_profile_settings.htm&language=en_US
This was selected as the best answer
MJ Kahn / OpFocusMJ Kahn / OpFocus
Thanks very much by your prompt and helpful reply!

To nit-pick, it's not that you cannot include standard object or field permissions; it's that if you do, they don't all make it through to the target org. (Odly enough, some of the standard fields I added to the permission set for my managed package do appear in the permission set in the target org, but not all of them.) It would be helpful if, when you tried to add such a permission to a managed package, you got an error (or at least a warning) message. 

But again, thank you for your answer!