Lead Settings
Lead Settings is the Setup-area page in Salesforce where admins configure org-wide behaviour for the Lead object: the default Lead owner for unassigned records, Lead conversion field mapping, the Web-to-Lead email response template, retention settings for converted leads, and the toggle that allows Lead reassignment from queue to user.
Definition
Lead Settings is the Setup-area page in Salesforce where admins configure org-wide behaviour for the Lead object: the default Lead owner for unassigned records, Lead conversion field mapping, the Web-to-Lead email response template, retention settings for converted leads, and the toggle that allows Lead reassignment from queue to user. It is the single most overlooked configuration area in Sales Cloud, because most admins build leads first and discover Lead Settings later when conversion behaviour does not match what the business expected.
The page lives under Setup, Object Manager, Lead, Lead Settings (or directly via Setup, Quick Find, Lead Settings). The settings here change behaviour for every Lead in the org, retroactively in some cases. Editing Default Lead Owner reassigns existing unowned leads. Editing field mapping changes which Lead field values flow into the Account, Contact, and Opportunity at conversion. Editing retention changes how converted leads display in reports. Treat Lead Settings as a project, not a one-click toggle.
How Lead Settings governs assignment, conversion, and retention across the entire Lead object
Default Lead Owner and the unassigned-lead catch
Every Lead has an Owner. If no assignment rule fires, the Owner defaults to whoever was set in Lead Settings as Default Lead Owner. Most orgs point this at a queue called Unassigned Leads or at a specific sales-ops user. Without it, the Lead falls to the user who created it, which usually means the integration user that loaded the lead in bulk, which means the sales team never sees the record. This is the single biggest reason real leads sit invisible for weeks; the default owner was never set on Lead Settings.
Lead conversion field mapping
Lead conversion creates an Account, a Contact, and optionally an Opportunity from a single Lead. Salesforce maps standard fields automatically (Lead.FirstName to Contact.FirstName), but custom Lead fields require explicit mapping in Lead Settings. Add a Lead.Industry__c custom field and forget to map it, and the value disappears at conversion. The Map Lead Fields button shows every custom Lead field and lets you pick the target Account, Contact, or Opportunity field. Audit this annually; new Lead fields without mapping are how data quietly disappears during conversion.
Web-to-Lead defaults and response template
Lead Settings holds two Web-to-Lead specific settings. The Default Response Template is the Email Template sent automatically to a new web lead via the assignment rule. The Default Lead Creator is the user record that Web-to-Lead leads are recorded under for audit (since web traffic has no logged-in user). Without a response template configured, new web leads silently submit without confirmation, which costs marketing programs measurable conversion. Without a default lead creator, system audit fields show "Automated Process" which makes triage harder.
Allow Lead reassignment from queue
A checkbox on Lead Settings: Allow Members to Accept Leads from Queue. Without it, sales reps can see leads in a queue but cannot take ownership; an admin or queue manager has to reassign. With it on, reps click Accept on any queue lead and become the owner. This is the single biggest Lead Settings toggle for sales productivity. Turn it on for orgs running a shared-queue inbound motion; leave it off for orgs where ops triages every lead manually.
Converted-Lead retention and the IsConverted field
Converted Leads stay in Salesforce permanently by default, with IsConverted = true. Reports filtered IsConverted = false return open leads; IsConverted = true returns historical conversions. Lead Settings does not have a retention toggle per se, but it links to the Lead Conversion configuration that controls which fields persist on the Lead after conversion. The standard pattern is to keep all data; clearing fields at conversion is a custom flow, not a built-in setting.
Enforce Validation and Triggers for Lead Conversion
Two settings interact at conversion time. Enforce Validation and Triggers checkbox controls whether Account, Contact, and Opportunity validation rules and triggers fire on the records created by conversion. Default off, which means conversion silently bypasses your business rules. Turning it on is correct for most orgs but breaks conversion flows that rely on partial data being inserted before validation. Test in sandbox before flipping the switch on production.
Person Account interaction with Lead conversion
Person Accounts (a single record representing both Account and Contact) interact with Lead conversion via a separate setting under Lead Conversion. When Person Accounts are enabled, the Convert button asks whether the Lead converts to a Business Account plus Contact or to a Person Account. Lead Settings does not control this directly; it routes through the Person Account configuration. B2C orgs running Person Accounts almost always want the Person Account default; B2B orgs want Business Account default.
Configuring Lead Settings before launching a Lead-driven sales process
Lead Settings is a one-page Setup screen with about eight fields. Configure it before loading any production leads. The configuration order below builds on itself; reversing steps creates gaps.
- Open Lead Settings
Setup, Quick Find, Lead Settings. The page lists every org-wide Lead behaviour. Most fields are single-pick (default owner, default response template); a few are toggles. There is no save warning if you leave halfway through, so plan to set every field in one session.
- Set Default Lead Owner
Pick a queue (Unassigned Leads is the typical name) or a sales-ops user. This is who gets every Lead not picked up by an assignment rule. Without this, leads default to whoever created the record, which is almost always wrong.
- Map custom Lead fields
Click Map Lead Fields. For each custom Lead field, pick the Account, Contact, or Opportunity field that receives the value at conversion. Skipping this is how custom data silently disappears.
- Configure Web-to-Lead defaults
Set Default Response Template to an Email Template that confirms receipt to the new web lead. Set Default Lead Creator to a specific user for audit. Without these, Web-to-Lead leads land with no auto-response and unclear audit attribution.
- Decide on Allow Members to Accept Leads from Queue
Turn on for shared-queue inbound motions where reps self-serve. Leave off for triaged motions where ops controls who gets what. Communicate the choice to sales managers; it changes day-to-day workflow.
User or queue receiving leads not picked by assignment rules. Typically a queue named Unassigned Leads or a sales-ops user.
One-to-one mapping of custom Lead fields to Account, Contact, or Opportunity fields. Audit annually as Lead schema evolves.
Email Template auto-sent to new web leads. Drives perceived responsiveness and downstream conversion rates.
Checkbox that runs validation rules and triggers on records created by Lead conversion. Off by default; turn on for production-quality orgs.
- Without a Default Lead Owner, every unassigned lead defaults to whoever created the record (usually the integration user), which means sales never sees it.
- Custom Lead fields without mapping silently lose their values at conversion. Audit Map Lead Fields whenever new Lead fields are added.
- Enforce Validation and Triggers is off by default. Conversion bypasses validation rules and triggers on Account, Contact, and Opportunity unless you turn it on.
- Allow Members to Accept Leads from Queue changes day-to-day rep workflow. Communicate before flipping.
- Person Account orgs route Lead conversion through a separate Person Account setting. Lead Settings alone does not control whether new converts become Business or Person accounts.
Trust & references
Cross-checked against the following references.
- Customize Lead SettingsSalesforce Help
- Map Lead Fields for ConversionSalesforce Help
Straight from the source - Salesforce's reference material on Lead Settings.
- Convert Leads to Accounts, Contacts, and OpportunitiesSalesforce Help
- Web-to-Lead SetupSalesforce Help
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What metric would Lead Settings typically help improve?
Q2. How does Lead Settings support the sales process in Salesforce?
Q3. Which Salesforce Cloud is Lead Settings primarily part of?
Discussion
Loading discussion…