Study guide

8.4 List Views, Kanban, Path, and User Adoption Tools

Salesforce Admin Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Platform Administrator Orientation and Official Source Control

1.1 Credential Name, Current Outline, and Search Language 1.2 Exam Format, Fee, Score, and Reference Rules 1.3 Trailhead, Trailhead Academy, and Pearson VUE Delivery Workflow 1.4 Domain Weights, Agentforce, and Study Prioritization 1.5 Maintenance Modules, Credential Ethics, and Exam Security 1.6 Developer Edition, Trailhead Playground, and Practice Bank Workflow

2 Chapter 2: Configuration, Setup, User Management, and Org Controls

2.1 Company Information, Fiscal Year, Business Hours, and Locale 2.2 User Records, Licenses, Profiles, Permission Sets, and Login Access 2.3 Login Security, Session Settings, and Identity Basics 2.4 Setup Navigation, Release Readiness, and Change Control 2.5 UI Settings, Home Pages, Apps, and Navigation 2.6 Configuration and Setup Case Lab

3 Chapter 3: Security, Access, Identity, and Sharing Model

3.1 Org-Wide Defaults, Roles, Sharing Rules, and Teams 3.2 Profiles, Permission Sets, Permission Set Groups, and Muting 3.3 Field-Level Security, Page Layouts, and Dynamic Forms 3.4 Record Access Troubleshooting and Login-As Workflow 3.5 Identity, Login History, MFA, and Session Risk 3.6 Data Visibility, Reporting, and Analytics Security 3.7 Security and Access Case Lab

4 Chapter 4: Object Manager, Lightning App Builder, and Data Modeling

4.1 Standard Objects, Custom Objects, and Schema Fit 4.2 Fields, Formulas, Rollups, Validation, and Requiredness 4.3 Lookup, Master-Detail, and Junction Relationships 4.4 Record Types, Business Processes, Page Layouts, and Lightning Pages 4.5 Dynamic Forms, Dynamic Actions, and User Experience 4.6 Schema Change Risk, Data Quality, and Deployment Readiness 4.7 Object Modeling Case Lab

5 Chapter 5: Sales, Marketing, Service, and Support Applications

5.1 Lead, Campaign, Account, Contact, and Opportunity Flow 5.2 Sales Processes, Path, Products, Price Books, and Forecasting 5.3 Case Management, Queues, Assignment, Auto-Response, and Escalation 5.4 Knowledge, Entitlements, Service Console, and Support Productivity 5.5 Sales-Service Data Quality and Automation Boundaries 5.6 Application Configuration Troubleshooting 5.7 Sales and Service Applications Case Lab

6 Chapter 6: Data and Analytics Management

6.1 Data Import Wizard, Data Loader, Export, and Backup 6.2 Duplicate Management, Validation, and Data Quality Controls 6.3 Data Transfer, Ownership, Mass Update, and Mass Delete 6.4 Report Types, Filters, Summary Formulas, and Buckets 6.5 Dashboards, Components, Subscriptions, and Sharing Impact 6.6 Analytics Security, Visibility, and Executive Reporting 6.7 Data and Analytics Case Lab

7 Chapter 7: Automation, Flow, Approval, and Operational Processes

7.1 Automation Tool Selection and Order of Execution 7.2 Flow Builder: Screen, Record-Triggered, Scheduled, and Autolaunched Flows 7.3 Approval Processes, Email Alerts, and Notification Patterns 7.4 Validation Rules, Assignment Rules, and Escalation Rules 7.5 Automation Testing, Debugging, and Governance 7.6 Automation Performance, Recursion, and Maintainability 7.7 Automation Case Lab

8 Chapter 8: Productivity, Collaboration, Mobile, and AppExchange

8.1 Activities, Tasks, Events, Calendar, and Email Productivity 8.2 Chatter, Feeds, Groups, Notifications, and Collaboration Governance 8.3 Salesforce Mobile Navigation, Actions, and Page Design 8.4 List Views, Kanban, Path, and User Adoption Tools 8.5 AppExchange Evaluation, Installation, Permissions, and Risk 8.6 Productivity and Collaboration Case Lab

9 Chapter 9: Agentforce for Platform Administrators

9.1 Agentforce Use Cases, Admin Boundaries, and Fit 9.2 Trusted AI, Security, Data Access, and Permission Implications 9.3 Agent Builder, Prompt Builder, and Grounding Concepts 9.4 Testing, Deployment, Monitoring, and Feedback Workflows 9.5 Agentforce Service, Sales, and Internal Productivity Scenarios 9.6 Agentforce Risk, Troubleshooting, and Governance 9.7 Agentforce Case Lab

10 Chapter 10: Integrated Salesforce Admin Scenario Labs

10.1 New Sales Org Setup Integrated Lab 10.2 Service Team Case Management Integrated Lab 10.3 Data Quality and Analytics Integrated Lab 10.4 Security, Access, and Reporting Integrated Lab 10.5 Flow Automation and Change Control Integrated Lab 10.6 Agentforce and Adoption Integrated Lab 10.7 Full Admin Simulation Strategy

11 Chapter 11: Final Review, Maintenance, and Test-Day Strategy

11.1 Final 30-Day Salesforce Admin Review Plan 11.2 Trailhead Playground Hands-On Drill Plan 11.3 105-Minute Exam Timing, Flagging, and Review Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Maintenance Modules and Next Certifications 11.6 Salesforce Admin Final Mixed Review

8.4 List Views, Kanban, Path, and User Adoption Tools

Key Takeaways Explain This Topic AI

List views and Kanban are productivity surfaces for focused work queues, not just alternate ways to display records.

Path improves adoption when stages, key fields, and guidance reflect the actual process users must follow.

Admins should combine configuration, reporting, training, and feedback loops to support adoption instead of relying on announcements.

Inline edit, mass actions, list view sharing, and Kanban updates must be evaluated against permissions, record types, validation rules, and automation.

Last updated: May 2026

Work surfaces, not decoration

List views are one of the most important adoption tools in Salesforce because they tell users what to work next. A queue of new leads, overdue tasks, high-priority cases, stalled opportunities, expiring contracts, or accounts missing next steps can change behavior more effectively than a training slide. The admin should design list views around action: who owns the record, what status it is in, what date makes it urgent, and what field tells the user the next move.

List view governance matters because unmanaged list views become clutter. Users may create personal views with unclear filters, duplicate names, or outdated assumptions. Public list views can help teams standardize work, but the admin should decide who can create, edit, and share them. Sensitive data should not be exposed by adding fields to a public list view if the audience lacks a business need, even though field-level security still controls actual field visibility.

Tool Best use Admin check

List view Focus a user or team on a filtered record set Filters, fields, sharing, inline edit eligibility, and naming.

Kanban Move records visually by status, stage, or owner-related workflow Record type, picklist values, summary fields, validation, and automation.

Path Guide users through a defined process step Key fields, guidance text, stage values, record types, and business ownership.

Prompts and guidance where available Coach users inside the app Targeting, frequency, accessibility, and retirement date.

Favorites and pinned views Speed access to common work Training and cleanup expectations.

Reports and dashboards Monitor adoption and process quality Data definitions, running user, folder access, and refresh cadence.

Kanban is useful when the object has a status-like field and users benefit from seeing work grouped visually. Opportunities by stage, cases by status, leads by status, and tasks by owner or status can all be useful. The admin should verify whether users can drag records between columns, whether validation rules or required fields block stage changes, and whether automation runs when a value changes. Kanban is not just visual; it can update data.

Path is a guided process feature. It can show key fields and guidance for success at each stage or status. A good Path reflects the organization's real process language. For an opportunity, early stages may emphasize qualification fields and discovery notes, while later stages may require legal review, primary contact, next step, close plan, and competitor information. For cases, Path may guide triage, investigation, customer response, resolution, and closure quality.

Adoption workflow for administrators

Adoption is an admin support workflow, not a one-time launch event. If a team is not updating opportunities, the admin should ask whether the page makes the right fields easy, whether list views show stale records, whether Path guidance matches the actual sales process, whether managers review the same fields, and whether automation creates friction. Users follow systems that help them do real work and that managers reinforce consistently.

Adoption design checklist:

Choose one target behavior, such as closing cases with complete resolution details.

Identify the objects, fields, stages, and user groups involved.

Build or revise list views that expose records needing action.

Configure Path guidance and key fields for each meaningful stage or status.

Add quick actions, dynamic visibility, or validation only where they support the behavior.

Create reports or dashboards that managers will actually use in coaching.

Train with realistic records, then collect support tickets and user feedback after launch.

Retire outdated prompts, list views, and guidance when the process changes.

Inline editing and mass changes can improve productivity, but they introduce control questions. Some fields cannot be inline edited because of field type, page configuration, record type differences, dependent picklists, or other constraints. Even when inline edit is available, validation rules and automation still apply. A user moving several opportunities in Kanban may trigger flows, approval requirements, forecast changes, notifications, or required-field errors. The admin should test the bulk workflow before telling users to rely on it.

Path guidance should be specific enough to shape behavior. Text such as Update the opportunity is not useful. Better guidance says what evidence belongs in the stage, which field must be current, what handoff is expected, and when the user should advance or move backward. However, the guidance should not try to replace the full training manual. Keep it short, action-oriented, and reviewed by the business owner.

Support teams should watch for adoption friction signals. If users repeatedly export list views to spreadsheets, maybe the list view lacks the right filters, fields, or inline actions. If managers ask for manual status updates, maybe dashboards are not trusted or records are not current. If users avoid Path stages, maybe stage names do not reflect reality or required fields are asked too early. The admin's job is to diagnose the operating model, not just add another required field.

Agentforce and AI features may appear in productivity conversations, but admin judgment still applies. AI-generated summaries, recommendations, or agents can support work only when the data is reliable, permissions are respected, use cases are approved, and outputs are tested. Do not use AI to paper over an unclear process. A poor stage model, stale activities, or unmanaged list views will still produce poor guidance.

Study trap: do not confuse adoption with login count. A user can log in every day and still manage deals in a spreadsheet. Better adoption measures include overdue tasks, opportunities with next steps, cases updated within service targets, records missing required process fields, and manager use of standard reports.