--- schema_version: "1" id: 2c60acee800838498a36c87267762cc887eed4935b368382ae249d11dcbf9b4a title: LeadConfigSettings collection: legacydeveloper version: current locale: en-us portal_url: https://docs.salesforce.com/legacydeveloper/current/en-us/api_meta/meta_leadconfigsettings.md canonical_url: https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_leadconfigsettings.htm source_site: developer.salesforce.com content_type: documentation content_hash: ed7cf6381502eb2dc007fbeae014489185d7f33fd758e829e00c127547fde8cf description: Represents configuration settings for Leads that control how they are converted and displayed, and what actions are available. This type extends the Metadata metadata type and inherits its fullName field. --- # LeadConfigSettings Represents configuration settings for Leads that control how they are converted and displayed, and what actions are available. This type extends the Metadata metadata type and inherits its fullName field. In the package manifest, all organization settings metadata types are accessed using the Settings name. See [Settings](https://developer.salesforce.com/docs/atlas.en-us.api_meta.meta/api_meta/meta_settings.htm "Represents the organization settings related to a feature. For example, your password policies, session settings and network access controls are all available in the SecuritySettings component type.") for details. ## File Suffix and Directory Location LeadConfigSettings values are stored in the LeadConfig.settings file in the settings folder. The .settings files are different from other named components because there’s only one settings file for each settings component. ## Version LeadConfigSettings is available in API versions 47.0 and later. ## Fields

Field Name	Field Type	Description
doesEnableLeadConvertDefaultSubjectBlankTaskCreation	boolean	Configures whether tasks without a subject are created during lead conversion. If `true`, tasks are created when the default subject field has no value. If `false`, only tasks with a subject are created.
doesHideOpportunityInConvertLeadWindow	boolean	Hides the opportunity section of the Convert Lead window during lead conversion. Default value is `false`.
doesPreserveLeadStatus	boolean	If your org uses record types, the lead status changes to the lead status value of the new owner's record type during conversion. Set doesPreserveLeadStatus to `true` to preserve the value of the lead status during conversion. Orgs that use record types can create a lead process that allows different lead status values for different record types. If doesPreserveLeadStatus is `false`, the lead status might change during lead conversion if the new owner's record type has a different default value for lead status. Default value is `true`.
doesSelectNoOpportunityOnConvertLead	boolean	Prevents an opportunity from being created when the lead is converted. Default value is `false`.
doesTrackHistory	boolean	Enables field history tracking for leads. When field history tracking is enabled, users can choose the fields they want to track. Default value is `false`.
enableConversionsOnMobile	boolean	Lets a user convert leads on their mobile devices. The Convert Lead action converts qualified leads to contacts. Default value is `true`.
enableOrgWideMergeAndDelete	boolean	Lets a user merge and delete leads. The user must also have the Public Read/Write/Transfer permission. Default value is `false`.
relateEmailsToContactOnConvert	boolean	Associates the lead's emails with the contact that it's converted to. Default value is `false`.
shouldLeadConvertRequireValidation	boolean	Enforces validation rules when converting leads. Default value is `true`.
shouldSendNotificationEmailWhenLeadOwnerUpdatesViaApexInLEX	boolean	Indicates whether an email notification is sent when the lead owner is updated through Apex in Lightning Experience. Default value is `false`.

## Declarative Metadata Sample Definition The following is an example of the LeadConfigSettings type: false false true false false true false true false ## Example Package Manifest The following is an example package manifest used to deploy or retrieve the LeadConfig settings metadata for an organization: