This is Part 14 of the Salesforce series. In earlier posts, we covered core configuration topics like objects, fields, page layouts, and quick actions. Now we turn to one of Salesforce’s most user-friendly features: Paths. Paths give your users a visual roadmap through a business process, showing them exactly where a record stands and what needs to happen next.
What Are Paths and When to Use Them?
A Path is a visual component in Salesforce Lightning Experience that displays the stages of a picklist field as a horizontal progress bar at the top of a record page. Each step in the path can surface Key Fields (the most important fields to fill in at that stage) and Guidance for Success (tips, instructions, or best practices written by the admin).
What a Path Looks Like to End Users
When a user opens a record with a path enabled, they see a horizontal bar stretching across the top of the page. Each segment of the bar represents a picklist value (such as an Opportunity stage or a Lead status). The current stage is highlighted, completed stages appear filled in, and future stages are outlined. Below the highlighted stage, a dropdown panel can expand to reveal key fields and coaching text.
Think of it as a visual GPS for your business process. The user always knows where they are, what they should be doing now, and what comes next.
When to Use Paths
Paths are ideal when:
- Your process is sequential. Records move through a defined series of stages (e.g., Prospecting to Closed Won).
- Users need coaching. New reps or cross-functional teams benefit from contextual tips at each step.
- Data quality matters. Surfacing key fields at each stage nudges users to fill in critical information before advancing.
- You want to reduce training overhead. Embedded guidance means users learn while they work.
Paths are not a replacement for validation rules or automation. They are a guidance layer. A user can still skip stages or leave key fields empty unless you enforce requirements through other mechanisms.
How Paths Relate to Sales Processes
A common point of confusion is the relationship between Paths and Sales Processes. They serve different purposes and work together.
| Aspect | Sales Process | Path |
|---|---|---|
| Purpose | Controls which picklist values are available for a given record type | Provides visual guidance through those picklist values |
| Where configured | Setup > Sales Processes | Setup > Path Settings |
| Effect on data | Restricts the stage values a user can select | Does not restrict anything; only displays and coaches |
| Applies to | Opportunity Stage field only | Any picklist field on any standard or custom object |
| Record type link | Directly linked to a record type | Can be linked to a record type or apply globally |
In practice, you often create a Sales Process first to define which stages are relevant for a particular type of Opportunity, and then create a Path on top of that to guide users through those stages with key fields and coaching content.
How to Set Up a Path
Step 1: Enable Path Settings
- Navigate to Setup and search for Path Settings in the Quick Find box.
- Click Path Settings.
- Toggle the Enable switch to turn on Paths for your org.
- Optionally, check Remember User’s Path Preferences so that the key fields and guidance panel stays expanded or collapsed based on each user’s last interaction.
Step 2: Create a New Path
- On the Path Settings page, click New Path.
- Fill in the following details:
| Field | Description | Example |
|---|---|---|
| Path Name | A label for this path (internal reference) | Opportunity Sales Path |
| API Name | Auto-populated from the path name | Opportunity_Sales_Path |
| Object | The object this path applies to | Opportunity |
| Record Type | Optionally restrict to a specific record type | B2B Opportunity |
| Picklist | The picklist field whose values become the steps | Stage |
- Click Next.
Step 3: Configure Each Step
For each picklist value (step), you can configure two things:
Key Fields
These are existing fields on the object that you want to highlight at this stage. For example, at the “Qualification” stage of an Opportunity, you might surface:
- Budget Confirmed
- Decision Maker Identified
- Discovery Completed
Key fields appear in the expandable panel below the path step. They are not required by default. To make them truly required, combine paths with validation rules or required fields on the page layout.
You can add up to 5 key fields per step.
Guidance for Success
This is a rich-text area where you can write coaching content. Examples include:
- Step-by-step instructions (“Schedule a discovery call and document pain points in the Description field.”)
- Links to internal resources (“Review the [Qualification Playbook] before advancing.”)
- Checklists (“Confirm budget, timeline, and decision-making authority.”)
- Tips (“Deals at this stage typically close within 30 days. Follow up weekly.”)
Guidance for Success supports bold, italic, bulleted lists, numbered lists, and hyperlinks.
Step 4: Enable Confetti Celebrations (Optional)
On the final configuration screen, you can choose to celebrate when a user reaches a specific step. Salesforce will display a confetti animation on the screen when the record reaches the designated stage.
Common celebration triggers:
| Object | Celebration Stage | Why |
|---|---|---|
| Opportunity | Closed Won | Deal is booked |
| Lead | Converted | Lead became a contact and opportunity |
| Case | Closed | Issue resolved |
| Custom Object | Final Status | Process complete |
Confetti is a small but meaningful morale booster for sales and service teams. It reinforces positive outcomes and makes the tool feel rewarding.
Step 5: Activate the Path
After configuring all steps, click Activate. Only one active path can exist per object-record type-picklist combination. If you need to make changes later, you can deactivate the path, edit it, and reactivate.
How to Add a Path to a Page Layout
Creating a path does not automatically make it visible on record pages. You need to add the Path component to the Lightning record page using the Lightning App Builder.
Steps to Add the Path Component
- Navigate to any record of the relevant object (e.g., open an Opportunity).
- Click the gear icon in the top-right corner and select Edit Page to open the Lightning App Builder.
- In the component panel on the left, find the Path component under the “Standard” section.
- Drag the Path component to the top of the page (it is designed to sit at the very top of the record page, spanning the full width).
- Click Save and then Activate the page.
- Choose the activation scope: assign the page to the org default, a specific app, or a combination of app, record type, and profile.
Important Notes on Page Layout Placement
- The Path component is meant to be placed in the header region of the page. Placing it in a sidebar or narrow column will cause it to render poorly.
- If no active path exists for the object-record type-picklist combination, the Path component will simply not render. It will not throw an error.
- You can have the Path component on the page even if you have not yet created a path. It will appear once you activate one.
Paths for Different Objects
Paths are not limited to Opportunities. You can create paths on any standard or custom object that has a picklist field. Here are common use cases:
Opportunity Paths
The most common use case. Path steps correspond to the Stage field. Combined with a Sales Process, this guides reps through the entire deal cycle.
Example stages and guidance:
| Stage | Key Fields | Guidance |
|---|---|---|
| Prospecting | Lead Source, Description | Research the company. Identify at least two stakeholders. |
| Qualification | Budget, Authority, Need, Timeline | Complete the BANT framework. Schedule a discovery call. |
| Proposal/Price Quote | Amount, Expected Close Date | Send a formal proposal. Confirm pricing with your manager. |
| Negotiation | Discount Reason, Competitor | Address objections. Get legal review if custom terms are needed. |
| Closed Won | Contract Signed Date | Celebrate! Ensure handoff to the onboarding team. |
Lead Paths
Path steps correspond to the Lead Status field. This is especially useful for teams with SDRs/BDRs who need a repeatable qualification process.
Example statuses: New, Contacted, Working, Qualified, Converted, Unqualified.
Case Paths
Path steps correspond to the Status field. Service teams use this to ensure consistent case handling.
Example statuses: New, In Progress, Waiting on Customer, Escalated, Closed.
Custom Object Paths
If you have a custom object like Onboarding__c with a picklist field called Onboarding_Stage__c, you can create a path on it. This is powerful for internal business processes that are unique to your organization.
Example: An employee onboarding object with stages like Offer Accepted, Background Check, Equipment Ordered, Training Scheduled, Onboarded.
Record Type-Specific Paths
One of the most powerful aspects of Paths is the ability to create different paths for different record types on the same object. This means you can tailor the guidance and key fields to the specific business process each record type represents.
Example: Opportunity Record Types
| Record Type | Path Focus | Stages |
|---|---|---|
| New Business | Full sales cycle with heavy qualification guidance | Prospecting, Qualification, Proposal, Negotiation, Closed Won/Lost |
| Renewal | Streamlined path focused on retention | Renewal Review, Customer Contact, Renewal Sent, Closed Won/Lost |
| Upsell | Expansion-focused guidance | Needs Assessment, Proposal, Closed Won/Lost |
How It Works
When you create a path, you select the record type it applies to. If you leave the record type blank, the path applies to all record types that do not have a specific path assigned. Salesforce follows this precedence:
- Path matching the exact record type is used first.
- If no record type-specific path exists, the default (no record type) path is used.
- If no path exists at all, the Path component is hidden.
Best Practices for Path Content
What to Include in Guidance for Success
The guidance text is your opportunity to embed tribal knowledge directly into the workflow. Here are content strategies that work well:
For Sales Teams:
- Discovery question templates
- Objection-handling tips for each stage
- Links to relevant case studies or collateral
- Approval thresholds (“Discounts over 15% require VP approval”)
- Competitive intelligence reminders
For Service Teams:
- Troubleshooting steps for common issues
- Escalation criteria and contacts
- SLA reminders (“First response must be within 4 hours for Priority 1 cases”)
- Links to knowledge articles
For Operations Teams:
- Compliance checklists
- Required documentation at each stage
- Links to internal process documents
- Handoff instructions between teams
Writing Effective Guidance
| Do | Avoid |
|---|---|
| Keep each step’s guidance concise (3-5 bullet points) | Writing paragraphs of text that users will skip |
| Use action verbs (“Confirm budget”, “Schedule call”) | Vague language (“Make sure things are good”) |
| Include links to resources | Assuming users know where to find documents |
| Update guidance regularly as processes change | Setting it and forgetting it |
| Tailor guidance to the audience’s experience level | Writing for experts when most users are new |
Key Field Selection Strategy
Choose key fields that:
- Are critical at that specific stage (not just important in general).
- Drive the decision to advance to the next stage.
- Are frequently left empty without a nudge.
- Are not already prominent on the page layout.
Remember the limit of 5 key fields per step. If you need more, it might indicate that your page layout needs restructuring rather than adding more key fields to the path.
Limitations and Gotchas
Understanding the constraints of Paths will save you from frustration during implementation.
Technical Limitations
| Limitation | Detail |
|---|---|
| One active path per combination | Only one path can be active for a given object + record type + picklist combination |
| Lightning Experience only | Paths are not available in Salesforce Classic |
| Picklist fields only | Paths can only be built on picklist fields, not checkboxes, lookups, or other field types |
| 5 key fields per step | You cannot surface more than 5 fields per step |
| No automation triggers | Moving along a path does not trigger flows, process builders, or Apex by itself. The underlying field change does. |
| Rich text limitations | Guidance for Success supports basic formatting but not images, videos, or complex HTML |
| No branching | Paths are linear. You cannot create conditional branches based on field values |
Common Gotchas
-
Path does not appear on the page. The most common issue. Ensure the Path component has been added to the Lightning record page via Lightning App Builder and that the page is activated.
-
Path shows wrong steps. Check that the correct Sales Process (for Opportunities) is assigned to the record type. The path displays the picklist values available to the record, which are filtered by the Sales Process.
-
Confetti does not fire. Confetti only triggers when a user manually changes the picklist value to the celebration step. If the change happens via automation (Flow, Apex, data import), confetti will not appear.
-
Key fields are not enforced. Paths only surface key fields as suggestions. They do not make fields required. Use validation rules or required fields on the page layout if you need enforcement.
-
Users skip stages. By default, paths allow users to jump to any stage. If you need to enforce a sequential process, you must implement validation rules or flows that prevent skipping.
-
Editing an active path. You must deactivate a path before editing it. This means the path temporarily disappears from record pages. Plan edits during low-usage hours.
-
Path and picklist value mismatch. If you add or remove picklist values after creating the path, you need to update the path to reflect the new values. The path does not auto-sync with picklist changes.
-
Dependent picklists. Paths do not account for dependent picklist logic. The path always shows all values for the selected picklist, regardless of controlling field values.
Practical Scenario: Setting Up an Opportunity Path
Let us walk through a complete real-world example.
Scenario: Your company has two Opportunity record types: “New Business” and “Renewal.” You want to create paths for both.
New Business Path
-
Go to Setup > Path Settings and click New Path.
-
Name it “New Business Sales Path.”
-
Select Opportunity as the object, New Business as the record type, and Stage as the picklist.
-
Configure each stage:
Prospecting:
- Key Fields: Lead Source, Description
- Guidance: “Research the prospect’s website and recent news. Identify at least two contacts. Log your outreach activities.”
Qualification:
- Key Fields: Amount, Close Date, Next Step
- Guidance: “Confirm budget, authority, need, and timeline. Schedule a discovery call. Update the Amount field with your best estimate.”
Proposal/Price Quote:
- Key Fields: Amount, Probability, Competitor
- Guidance: “Generate a quote using CPQ. Send the proposal to the economic buyer. Follow up within 48 hours.”
Negotiation/Review:
- Key Fields: Discount Reason, Next Step
- Guidance: “If discount exceeds 15%, get VP approval. Loop in legal for non-standard terms. Set a firm decision date.”
Closed Won:
- Key Fields: Contract Signed Date
- Guidance: “Ensure the signed contract is attached. Notify the onboarding team via the handoff Chatter group.”
- Enable Confetti Celebration.
-
Activate the path.
-
Open the Opportunity Lightning record page in App Builder, add the Path component to the top of the page, and activate the page for the New Business record type.
Renewal Path
Repeat the process with different stages, key fields, and guidance tailored to the renewal process. Since renewals are typically shorter and more predictable, the guidance can focus on customer health, pricing changes, and contract terms.
Summary
Paths are one of the simplest yet most impactful features you can configure in Salesforce. They cost nothing extra, take minutes to set up, and immediately improve user adoption and data quality. The key takeaways:
- Paths provide a visual progress bar tied to any picklist field on any object.
- Use Key Fields to surface the most important data points at each stage.
- Use Guidance for Success to embed coaching, checklists, and links directly in the workflow.
- Create record type-specific paths to tailor guidance for different business processes.
- Paths are a guidance layer, not an enforcement mechanism. Combine them with validation rules and required fields for data integrity.
- Remember the limitations: Lightning only, one active path per combination, no branching, and no automation triggers from the path itself.
What’s Next?
In the next post, we will explore Approval Processes in Salesforce — how to build multi-step approval workflows that route records to the right people, enforce business rules, and track approval history. If Paths guide users through a process, Approval Processes ensure the right checkpoints are enforced before a record can move forward. Stay tuned!