Contents:

• Overview
• Key Definitions
• Opening the Journey List View
• Understanding the Journey List
• Focusing Your List
• Opening a Journey
• Managing Journey Ownership, Status, and Lifecycle
• Journeys on Account and Opportunity Records
• Considerations
• Administrator Setup
• Troubleshooting
• Summary

 

Overview

The Journey List View is the starting point for working buying group motions in Salesforce. It brings every Journey you have access to into a single list, with the context you need to decide which one to work next: recent signal activity, ownership, status, linked Opportunity, and how much of the buying group has been identified.

Rather than opening Accounts or Journey records one at a time to see what is happening, you can review every motion in one place, narrow the list to the Journeys you own, and open the full Journey without leaving the list.

This article covers both sides of the Journey List View. Sellers and managers can work through the sections below on finding, focusing, and working Journeys. Salesforce administrators can go straight to Administrator Setup for adding the list view to Salesforce, granting access, and defining Journey Status values.

Key Definitions

• Buying Group Journey: A custom object created and managed by LeanData that serves as a container for potential and confirmed buying group members and the signals associated with those members. A Journey can be linked with an Opportunity and belongs to a specific Account.
• Potential Member: A Lead or Contact that LeanData has identified based on your configured criteria, but that a user has not yet confirmed as a Buying Group Member.
• Buying Group Member: A confirmed member of the buying group. Each member has a Role, and those Roles map to Contact Roles on a linked Opportunity.
• (Buying Group) Signal: A sales or marketing engagement record, such as a Campaign Member, Task, or Event, that LeanData captures for a potential or confirmed member.
• Segment: A categorization of Journeys based on configurable characteristics, used to support different selling motions. An Account can have one Journey per Segment.
• Journey Owner: The Salesforce user responsible for working the Journey.
• Journey Status: A picklist your administrator defines to reflect where the Journey sits in your team's workflow, such as Assigned to SDR, SDR Working, or Sales Qualified.

 

Opening the Journey List View

The Journey List View is available from the Journeys tab in Salesforce. Your administrator controls the tab name and which apps and profiles it appears in, so the exact label may differ in your org.

The same experience is also embedded on Account and Opportunity record pages when your administrator adds it there. See Journeys on Account and Opportunity Records below.

 

Understanding the Journey List

Each row in the list represents one Buying Group Journey and shows the context you need to triage it without opening the record:

• Journey: The Journey name, formatted as [Account Name] : [Segment Name].
• Account: The Salesforce Account the Journey belongs to.
• Segment: The Segment that created the Journey, which tells you which selling motion it represents.
• Journey Owner: The user responsible for the Journey.
• Journey Status: Your team's workflow status for the Journey.
• Opportunity: The linked Opportunity and its stage, when one is linked.
• Buying group coverage: How many of your ideal Roles have been filled by confirmed members.
• Recent signal activity: When the most recent signal was captured, so you can tell an active motion from a stale one.

 

Focusing Your List

The list opens with every Journey you have permission to see. Four controls let you narrow it, and they work together. You can search inside a filtered list, group a searched list, and so on.

My Journeys

Switch on My Journeys to show only the Journeys you own. This is the fastest way to get to the buying motions you are responsible for. The full list remains available when you switch it back off, so you can still see across your team when you need to.

Search

Use the search box to find a Journey by Account name or Journey name. This is the quickest path when you already know the account you want to work.

Group By

Use Group By to organize rows into collapsible groups. Grouping by Journey Owner creates one group per owner, which is useful when you are reviewing work across a team, and grouping by Segment separates different selling motions.

Filters

Add filters using Account and Journey fields, including custom fields in your org. Because filters draw on your own Salesforce fields, you can scope the list to the territories, industries, tiers, or segments your team works.

To add a filter:

1. Click Filter.
2. Select the field you want to filter on.
3. Select an operator and a value.
4. Add more conditions as needed.

Clear an individual filter to remove it, or clear all filters to return to the full list.

 

Opening a Journey

Select a row to open the Journey without leaving the list. The Journey opens in a side panel so your list stays in view, and you can expand it to a full screen view when you want more room. Closing the Journey returns you to the list exactly as you left it, with your search, grouping, and filters intact.

From the open Journey you get the full Journey Tracker experience, including potential members, confirmed members and their Roles, the activity feed, and the timeline. For details on those sections, see LeanData Journeys - Journey Record Page and Tracker.

Journeys can also be linked directly. A Journey link opens the Journey List View with that Journey selected, which is useful in Chatter posts, Slack messages, or Salesforce fields where you want to hand a specific buying motion to a teammate.

 

Managing Journey Ownership, Status, and Lifecycle

Assign a Journey Owner

Set the Journey Owner to the user responsible for working the buying motion. Reassign the owner when a Journey changes hands, for example when an SDR passes a qualified motion to an AE.

Set a Journey Status

Set the Journey Status to reflect where the Journey sits in your team's process. The available values, and their colors, are defined by your administrator to match how your team works, so they will be specific to your org.

Qualify a Journey

Mark a Journey as qualified or unqualified to record whether it represents a real buying motion worth working. Qualification is separate from Journey Status, which tracks progress, and from the Opportunity link, which tracks pipeline.

Close a Journey

Close a Journey when the buying motion is finished, for example when the linked Opportunity closes. Closing stops the Journey from collecting new signals and member activity.

Reopen a Journey

Closing a Journey is not permanent. If the buying motion picks back up, you can reopen the Journey and continue working it. Reopening returns the Journey to an active state and resumes signal and member tracking.

A reopened Journey keeps its history, so you do not start over. Confirmed members and their Roles, potential members, and the signals captured before the close remain on the Journey, and the Feed and Timeline continue to show the full story of the motion.

 

Journeys on Account and Opportunity Records

The same Journey experience is available directly on Account and Opportunity record pages when your administrator adds it:

• On an Account, you see the Journeys associated with that Account, which is useful when you are already researching the account and want the buying group picture in context.
• On an Opportunity, you see the Journey linked to that Opportunity, so you can check role coverage and recent engagement while you are working the deal.

Behavior matches the standalone tab, so anything you can do from the Journeys tab you can also do from the record page.

 

Considerations

• Filtering applies to the Journeys loaded in your list. In very large orgs, scope the list with search or filters rather than scrolling.
• Your view respects Salesforce permissions. If a Journey, Account, Opportunity, or field is not visible to you in Salesforce, it will not appear here.
• Search, grouping, My Journeys, and filters are stored per browser and do not follow you across devices.
• An Account can have one Journey per Segment, so an account working two product lines will appear once per Segment.

 

Administrator Setup

The rest of this article is for Salesforce administrators. It covers making the Journey List View available to your teams: adding the Journeys tab, placing the Journey experience on Account and Opportunity record pages, granting the right permissions, and defining the Journey Status values your team works with.

Adding the Journeys Tab

Add a tab so your teams can reach the Journey List View from Salesforce navigation.

Before you begin. The Journey List View also depends on org level LeanData configuration, including the Journey app base URL, API access settings, and a remote site setting. LeanData handles this configuration, so if the tab appears but the list does not load, contact LeanData Support to confirm it is in place before troubleshooting anything else.

1. From Salesforce Setup, go to Tabs.
2. Create the tab for the LeanData Journey List View. Create a Lightning Component Tab and select the LeanData Journey List View component.
3. Enter a Tab Label. LeanData Journeys is recommended.
4. Select a Tab Style and complete the remaining Salesforce prompts.
5. Save the tab.
6. Add the tab to the Salesforce apps your sales teams use, and set tab visibility for the appropriate profiles.
7. Confirm that those same profiles also have access to the Journey List View component. Tab visibility alone is not enough. See Configuring Permissions below.

Adding Journeys to Account and Opportunity Record Pages

Sellers work from Account and Opportunity records as well as from the Journeys tab. Adding the Journey component to those record pages gives them the same experience in context, as described in Journeys on Account and Opportunity Records above.

1. From Salesforce Setup, go to Object Manager and select Account or Opportunity.
2. Click Lightning Record Pages, open the page you want to edit, and click Edit.
3. In the Lightning App Builder, drag the LeanData Journey component onto the page. Adding it as its own Tab is recommended so it has dedicated space alongside the other record details.
4. Set the component Height. 800 pixels is a good starting point. Adjust it so the list displays without forcing users to scroll inside the component.
5. Save the page.
6. Click Activation and assign the page according to your org's setup, such as org default or specific apps, record types, and profiles.

Configuring Permissions

The Journey List View depends on Salesforce permissions in two places, and missing access is the most common cause of setup problems.

End user access

Users who work Journeys need:

• Access to the LeanData Journey List View Lightning component. In Setup, open the user's Profile and confirm the component is enabled for it.
• Read access to the LeanData Journey object and its related objects, so the list can display Journey, member, and signal data.
• Read access to the Account and Opportunity fields you expose through filters and columns.

Users who cannot see a Journey, an Account, an Opportunity, or a field in Salesforce will not see it in the Journey List View either.

Journey Owner access

Any user who may be assigned as a Journey Owner needs at least Read permission on the LeanData Journey object. Grant this through a permission set assigned to all owner eligible users.

Because the Journey is a custom object, users do not receive this access automatically the way they do for Leads and Contacts. Without it, Salesforce rejects the owner assignment and the change fails.

Configuring Journey Status

Journey Status lets your team track where a Journey sits in your own workflow, using values you define. Common examples are Assigned to SDR, SDR Working, Sales Working, Sales Qualified, and Recycled.

1. From Salesforce Setup, go to Object Manager and select LeanData Journey.
2. Go to Fields & Relationships and click New.
3. Create a Picklist field. Give it a clear name such as Status Label.
4. Add the status values your team uses.
5. Save the field.

 

Troubleshooting

A user cannot open the Journey List View

Confirm the user's profile has access to the LeanData Journey List View Lightning component. In Setup, open the user's Profile and check the component access there. A user who has the Journeys tab but not the component will see the tab and an empty page.

Assigning a Journey Owner fails

If assigning an owner returns an error, the user you are assigning most likely lacks Read access on the LeanData Journey object. Grant Read through a permission set and try again. See Configuring Permissions above.

Journeys are missing or the list looks incomplete

Check these in order:

1. Confirm the Segment that should create the Journeys is active. See LeanData Journeys - Settings Guide.
2. Confirm the user has Salesforce access to the underlying Accounts and Journey records.
3. Confirm no filters or the My Journeys toggle are limiting the view. Filters persist in the browser between sessions.

If the list is still incomplete after these checks, contact LeanData Support.

 

Summary

The Journey List View gives sellers and managers one place in Salesforce to see every active buying group motion, focus on the Journeys they own, and open the full Journey in context. Combined with Journey Owner, Journey Status, and qualification, it turns Journeys into a workflow your team can run day to day rather than a set of records to search through. Administrators set it up by adding the Journeys tab, placing the Journey component on Account and Opportunity record pages, granting component and object access, and defining the Journey Status values the team works with. Granting Journey Owner access during setup prevents the most common issue teams run into later.

For questions or additional assistance, please contact LeanData Support.