I've a requirement to deploy the below fields using ChangeSets from Sandbox to Production,

I have one field CaseMode__c visible to all profiles except two profiles and another custom field, OffsetHour__c that should be hidden for all profiles. These fields are available on Case Object.

Can I deploy these permissions with change sets or do I need to do this manually in production?

3 Answers 3


Since its a custom field include the fields as well as profiles also in the changeset to configure permissions .I would recommend all profiles along with this field in one changeset for deployment with permission same as the source org .

  • 2
    This is the key point - if you want to deploy a FLS rule on a permission set, you have to include the field it is referencing as well - even if you aren't pushing any changes to that field... Jan 2, 2015 at 17:29
  • @Mohith, how do you add profiles to a change set? There's a long list of things you can add (from Action to Zone), but there is no Profile in the list?
    – JannieT
    Aug 3, 2015 at 15:27
  • 1
    @JannieT That is done lower down on the edit page of the change set , in the section which currently is titled "Profile Settings For Included Components", by clicking the Add Profiles button. It leads to a page where you likely would select all the profiles.
    – ElHombre55
    Jul 6, 2022 at 18:58

If you add profile permissions to a change set, they'll carry over the permissions they have in the sandbox for all and only the objects in the change set. So if you're change set has just two fields plus all profiles, and you've set up the permissions already, it'll deploy the way you want.

That said, IMHO, change sets are a royal pain in this department. If I were in your shoes, I'd deploy the two fields as a change set, which by default makes them invisible to all profiles. Then go to CaseMode__c and use the set field level security button to make it visible to the desired profiles ...

  • When you say to deploy the two fields as a change set -> If you are referring to Salesforce Change Sets then deploying the fields without profile will make the fields visible to no-one once deployed. The FLS settings are unchecked when deployed without profiles which makes it a royal PITA. Unless you know of a trick....
    – Eric
    Aug 26, 2014 at 13:53

@Ralph : Make sure you have your requirements of having CaseMode__c visible to all profiles except two and another field OffsetHour__c that should be hidden for all profiles completed in your source ORG.

Now while creating a changeset add all the profiles and the two custom fields in the changeset. This will ensure that all the visibility/permissions related to the two fields will moved to the destination ORG.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .