For a new profile created in a sandbox and deployed with a change set it'll carry with it the settings for all other metadata in the change set plus all settings that aren't specifically metadata related, and everything else turned off. However most of them are already set up in some form or another. What determines the values for the rest of the settings?

  • Tab Settings
  • App Settings
  • Connected App Access
  • Custom Object Permissions
  • Article Type Permissions
  • Desktop Integration Client
  • Enabled Apex Classes
  • Enabled VisualForce Pages
  • Login IP Ranges


I'd tested this by deploying a new object along with a new profile. When deployed it carried over the following:

  • Name
  • Description
  • System Permissions (General and Administrative)
  • Settings for Custom Object

I would have expected everything else would be in some form of "off" status as appropriate for the permissions, but strangely it had a lot of other permissions enabled with no apparent logic, specifically:

  • Standard and Custom Tabs are randomly default off/default on/tab hidden
  • Custom Object Permissions mostly off, but randomly on for misc objects
  • Standard Object Permissions mostly on, but not all
  • Enabled Apex Classes, randomly enabled about half
  • Enabled Visualforce Pages, randomly enabled about half
  • Login IP Ranges, random set
  • Desktop Integration Clients all "On, updates w/o alerts"
  • 1
    I've run into this same exact issue recently and can't find a definitive answer from Salesforce documentation but what I believe is happening is, it inherits permissions from the standard user profile for anything not explicitly included in the change set. Compare what you are seeing to the standard user profile and see if it lines up. – ripper2020 Jun 17 '19 at 15:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.