I am working on migrating permissions from the Profiles to Permission sets and I am running into an issue, specific to managed apps that have their own custom permission sets. When you add a new field to a managed Object, in our case "change_machine_taxes", I can't add that new field to the managed packages Permission Set. You can't do it for any managed package.
So my question is, how should this be handled with SF move to Permission Sets. Do I have to create a brand new Custom Permission Set and include the objects of the managed package and give new Read, Edit, and so on for the object and then add the new field to that custom permission set? If so, doesn't that cause a conflict? As I have 2 permission sets that have duplicate permissions?
#Nonprofit #Salesforce Admin #Permissionset
FWIW @Kymberli Feng's Option B is my choice as well. Custom Permission Set that is only the custom/unmanaged that you've added, even if it's just checking "Read/Edit" on a single field. You don't have to do anything with object permissions, since the managed PS will cover. User would be assigned a Group that contains both the managed and custom permission set. I've gotten bitten by cloning too.
