Path Settings
Path Settings is the Salesforce Setup page where administrators turn on and configure Path, a visual component that shows where a record sits in a process.
Definition
Path Settings is the Salesforce Setup page where administrators turn on and configure Path, a visual component that shows where a record sits in a process. Path renders the values of a picklist (such as Opportunity Stage, Lead Status, or Case Status) as a horizontal progress bar across the top of a record page in Lightning Experience.
From Path Settings, an admin attaches up to five key fields and up to 1,000 characters of guidance to each step. They can also switch on celebrations so a burst of confetti fires when a record reaches a chosen value. The page is the single control point for every Path in the org.
How Path turns a picklist into a guided workflow
What Path actually displays
Path reads a picklist on an object and lays its values out as ordered steps. The current value is highlighted, the values before it read as completed, and the values after it read as upcoming. A user clicks a step to preview its guidance, then clicks Mark as Current Stage to move the record there, or Mark Status as Complete on the final step. The point is to make the process visible. A bare Stage picklist tells a rep the value but not what comes next or what the step requires. Path puts both on screen. Underneath the bar, Salesforce renders the key fields and guidance you assigned to whichever step is selected, so a rep editing an Opportunity in Negotiation sees exactly the fields and notes that belong to Negotiation. Path supports standard objects like Opportunity, Lead, Case, Contract, and Order, and it works on custom objects too. It only appears in Lightning Experience and in the mobile app, never in the old Classic interface, so an org still on Classic gets no benefit from it.
Key fields and guidance for success
Each step on a Path carries two kinds of content. Key fields are up to five fields that surface right under the progress bar, editable inline, so the data that matters at that step is one click away instead of buried in the Details tab. Guidance for success is a free text area that holds up to 1,000 characters per step. You can write tips, policy reminders, or links, and you can paste rich content like images or short instructions. The two together answer the rep question that kills pipeline accuracy: what does this stage need from me. A Prospecting step might surface the Amount and Close Date fields with guidance to confirm budget. A Negotiation step might surface a discount field with a reminder about approval thresholds. The record type and owner fields are special. They show in the key fields area but cannot be edited there, because changing them needs the Change Record Type action or the Details tab respectively. Plan each step as a small piece of content, not as a checkbox an admin fills in alone.
Celebrations and the confetti animation
Celebrations are the feature that makes Path feel rewarding. In Path Settings you toggle Enable Celebrations, move one or more picklist values into the Selected for Celebration list, and pick a frequency. The frequency controls how often the animation plays for a given user, with Always firing every time and the other options throttling it. When a record reaches a celebrated value, a short burst of confetti animates across the screen. A common setup celebrates the Closed Won stage so reps get a small payoff for closing a deal. Two limits trip people up. Celebrations do not support a picklist value whose API name contains a comma, so you remove the comma or recreate the value. Celebrations also do not fire on the Lead status Converted, because conversion follows a different path through the system. One more thing to know: celebrations and the key fields and guidance you configure also appear in the matching Kanban view for the same object, record type, and picklist, so the work you do in Path Settings carries over to that board for free.
Record types and the one-Path-per-type rule
Path is scoped to a record type. Each object can have one Path per record type, plus one Path for the master case when no record type applies. That rule shapes your design. If your Opportunity object has a New Business record type and a Renewal record type, you can build two separate Paths, each driven by the picklist values that record type actually uses. A rep working a Renewal sees the Renewal Path, and a rep working New Business sees theirs. The picklist behind a Path is usually the standard status field for the object, but any picklist that varies by record type can drive one. Deleting a record type also deletes the Path attached to it, so plan record type cleanups carefully. Because the picklist values are the steps, reordering or renaming values in the picklist changes the Path, and adding a value adds a step that has no guidance until you write some. Keep the picklist definition and the Path content in sync, or reps will hit blank steps.
Visibility, permissions, and field-level security
Path respects the same security model as the rest of the platform, which is easy to forget when a Path looks broken. A Path appears only when the running user can view the record, can see its record type, and can access every field used in the Path. If you add a key field that a profile cannot see through field-level security, the Path can fail to render for those users rather than just hiding that one field. The same applies to the picklist values themselves: a value restricted from a user changes what their Path shows. This is why a Path that works for an admin sometimes shows nothing for a sales rep. The fix is to check field-level security and picklist value access for the affected profile or permission set, not to rebuild the Path. Treat the Path component as a window onto data the user is already allowed to see. It grants no extra access of its own, and it never exposes a field a user could not otherwise open. When you test a Path, test it as a real user, not from a System Administrator login.
Where Path fits among related features
Path is one of a small family of process-visualization tools in Lightning Experience, and knowing the neighbors helps you place it. Kanban shows the same picklist as draggable columns across all records of an object, while Path shows it as a bar on a single record. The two share key fields, guidance, and celebrations, so configuring one benefits the other. Path is not Flow and not a Lightning component you build by hand. It is a declarative feature that an admin sets up in clicks, then drops onto a record page through the Lightning App Builder using the Path component. On a page assembled with Dynamic Forms, Path still sits at the top as a distinct component. Path also pairs naturally with validation rules, since the guidance you write at a step can warn reps about the rules that will fire when they try to advance. None of these replace Path. Each handles a different slice of the same goal, which is helping a user understand and move through a structured process without leaving the record they are working on.
How to set up Path in Path Settings
You configure Path entirely from Setup. Enable it once for the org, then build one Path per object and record type, adding key fields, guidance, and optional celebrations to each step.
- Open Path Settings and enable Path
In Setup, type Path Settings in Quick Find and open it. Click Enable, optionally turn on celebrations at the org level, then click Finish to reach the Path Settings home page.
- Create a new Path
Click New Path. Give it a name and an API name, then choose the object, the record type, and the picklist whose values will become the steps of the progress bar.
- Add key fields and guidance to each step
Select a step, add up to five key fields that should surface for it, and enter up to 1,000 characters of guidance for success. Repeat for every step that needs content.
- Configure celebrations
Toggle Enable Celebrations, move the picklist values you want to reward into the Selected for Celebration list, and choose a frequency such as Always so the confetti fires when a record reaches that value.
- Activate and add Path to the page
Set the Path to Active. Then open the record page in the Lightning App Builder and drop the Path component near the top so users see the progress bar when they open a record.
The object the Path runs on, such as Opportunity, Lead, Case, or a custom object that has a status-style picklist.
The record type the Path applies to. Each object allows one Path per record type, so pick the one whose users you are guiding.
The picklist whose values become the ordered steps. Usually the standard status field, like Stage on Opportunity or Status on Lead.
Up to five fields shown inline under the bar for the selected step, so critical data is editable without leaving the Path.
Up to 1,000 characters of tips, reminders, or links shown for the selected step to tell reps what that stage needs.
The picklist values that trigger the confetti animation and how often it plays, set per Path through Enable Celebrations.
- Path renders only when the user can view the record, its record type, and every field used, so a hidden key field can blank the whole Path for that profile.
- Celebrations will not fire on a value whose API name contains a comma, and they never fire on the Lead status Converted.
- Deleting a record type deletes the Path attached to it, and renaming or reordering the underlying picklist values changes the steps.
- Path is Lightning Experience and mobile only. Users still in Salesforce Classic see nothing, so confirm the org has moved off Classic first.
Prefer this walkthrough as its own page? How to Path Settings in Salesforce, step by step
Trust & references
Cross-checked against the following references.
- Guide Users with PathSalesforce
- Considerations and Guidelines for Creating PathsSalesforce
Straight from the source - Salesforce's reference material on Path Settings.
- Enable PathSalesforce
- PathAssistantSettings, Metadata API Developer GuideSalesforce
Hands-on resources to go deeper on Path Settings.
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 does enabling Path through the Path Settings page add to a record page?
Q2. Which kind of picklist does an admin choose to drive a Path inside Path Settings?
Q3. Why is configuring a good Path in Path Settings called a content-design exercise, not a solo task?
Discussion
Loading discussion…