When deploying change sets with new profiles, we're finding when the profile is created in the target environment, that extra object permissions are being added inadvertently. Why would this be happening and any idea how we can prevent it?
Hi @Casey Rio,
Profiles in change sets only include the permission related to objects in the change set. To ensure all permissions carry over, all objects need to be part of the change set. Which is to say all objects where the new profile should not have permissions available as part of the default profile.
It can be daunting depending on the release management process. I always used a newly refreshed sandbox as a bridge, pushing the updates from the development sandbox to the fresh sandbox. Then I replicate the change set from dev and add the object where permissions need to be managed.
HTH
Regards,
Scott S Nelson
