How to Customize the Salesforce Kanban View for Your Sales Process

The Salesforce Kanban view is a visual board that displays your CRM records as draggable cards organized into columns by stage, status, or any picklist field. It gives sales teams a real-time snapshot of their pipeline — where every deal stands, which ones need attention, and what's about to close. According to Salesforce's own data, teams that adopt visual pipeline tools like Kanban report up to 28% faster deal progression compared to traditional list-based views.

Here's what the Kanban view helps you do at a glance:

• See every open opportunity organized by sales stage
• Drag and drop deals from one stage to the next
• Spot stalled opportunities with built-in alert indicators
• Edit key fields directly from the Kanban card without opening the record
• Filter and sort your pipeline by owner, amount, close date, or custom fields

In this guide, you'll learn how to set up, customize, and optimize the Salesforce Kanban view to match your exact sales process — whether you're managing opportunities, leads, cases, or custom objects.

What Is the Salesforce Kanban View?

The Kanban view in Salesforce is a list view display option that turns your records into visual cards arranged in columns. Each column represents a value from a picklist field — like Opportunity Stage or Lead Status — and each card represents a single record.

The word "Kanban" comes from Japanese (看板), meaning "visual signal." Toyota's manufacturing teams pioneered the approach in the 1940s to track production flow. Salesforce brought this concept into its Lightning Experience in 2017 when it replaced the older Opportunity Board view.

What makes it different from the standard table layout? Three things stand out. First, you get spatial awareness — you can literally see where deals cluster and where gaps exist in your pipeline. Second, drag-and-drop stage changes mean reps update records in one motion instead of opening each record individually. Third, the built-in alert system flags deals that haven't been touched in 30 days, so nothing slips through the cracks.

Kanban View vs. List View vs. Split View

Choosing the right view depends on what you're trying to accomplish. Here's a quick breakdown:

In our experience working with sales teams at Minuscule Technologies, the Kanban view works best when reps need to manage 20–100 active deals and want a quick way to move them through stages. For large-scale data cleanup or reporting, the table view is still your go-to.

How to Enable the Kanban View in Salesforce Lightning

The Kanban view is available in Lightning Experience across all Salesforce editions — Essentials, Professional, Enterprise, Performance, Unlimited, and Developer. It is not available in Salesforce Classic, so you'll need to be on Lightning to use it.

Here's how to turn it on:

1. Navigate to any object's list view. For this walkthrough, let's use Opportunities. Click "Opportunities" in the navigation bar.
2. Select a list view from the dropdown. Pick any saved view except "Recently Viewed" — Kanban doesn't work with the default "Recently Viewed" lists. Choose something like "My Opportunities" or "All Opportunities."
3. Click the display icon in the upper-right corner of the list view (it looks like a small grid). Select "Kanban" from the dropdown options.
4. Salesforce will prompt you to configure your grouping and summary fields. Choose the picklist field for your columns (like "Stage") and an optional summary field (like "Amount").
5. Click "Save." Your Kanban board is ready.

Prerequisites and User Permissions

Before your team can start using Kanban, make sure these permissions are in place:

• "Read" permission on the object — users need at least this to see the Kanban view
• "Edit" permission on the object — required for drag-and-drop stage changes and inline editing
• "Create and Customize List Views" — so users can save their own Kanban configurations
• Kanban Settings permission — admins may need to enable this if it's restricted

One thing that catches admins off guard: the Kanban view respects all existing sharing rules, field-level security, and record types. If a user can't see certain records in list view, they won't see them in Kanban either. And records are separated by Record Type — each Record Type gets its own tab in the Kanban board.

How to Customize Your Salesforce Kanban View

This is where most teams stop at the defaults and miss out on real productivity gains. The Kanban view has three main customization levers: grouping fields, summary fields, and card field selection.

Change Grouping and Summary Fields

Click the gear icon in the upper-right corner of your Kanban view and select "Kanban Settings." You'll see two dropdown menus:

Group By — This determines your columns. For Opportunities, "Stage" is the obvious choice. But consider these alternatives for different scenarios:

• Lead Source — if you want to see deal distribution by channel
• Opportunity Owner — for managers reviewing team workload
• Type — to separate new business from renewals or upsells
• Forecast Category — to align with your forecasting process

The Group By field must be a picklist. If your process uses a custom picklist field (like "Deal Temperature" or "Approval Status"), you can group by that too.

Summarize By — This adds a total at the top of each column. Options include any currency or number field:

• Amount — shows total pipeline value per stage
• Expected Revenue — factors in probability
• Quantity — for volume-based sales
• None — if you just want the card count

In our work with sales organizations, we've found that grouping by Stage and summarizing by Amount gives the clearest picture for pipeline reviews. But for lead management, grouping by Lead Status and skipping the summary often works better.

Select the Right Card Fields for Your Sales Process

The Kanban card displays the first four columns from your underlying list view. This is critical: the fields you see on each card are determined by which columns you've selected in the table view — not by a separate Kanban setting.

To change what appears on your Kanban cards:

1. Switch back to the table (list) view
2. Click the "gear" icon → "Select Fields to Display"
3. Reorder your columns so the four most important fields come first
4. Switch back to Kanban view — your cards now show those fields

For an Opportunity Kanban view tailored to sales, we recommend these four fields in order:

1. Opportunity Name — always first for identification
2. Amount — so reps see deal value at a glance
3. Close Date — to spot upcoming deadlines
4. Account Name — for context on which customer the deal belongs to

For a Lead Kanban view, try: Lead Name, Company, Lead Source, Rating.

Use Filters to Focus Your Pipeline

Kanban views inherit the filters from the underlying list view. You can add up to 10 filter conditions to narrow down your board:

• Filter by Close Date to show only deals closing this quarter
• Filter by Amount to focus on high-value opportunities above a threshold
• Filter by Owner to see just your own deals or your direct reports' deals

You can also use the search bar at the top of the Kanban view to find specific records by keyword.

Pro tip: Create multiple saved list views with different filter combinations, then switch between them in Kanban. For example, "Q2 Pipeline Over $50K," "Stalled Deals — No Activity 14 Days," or "New Business — Discovery Stage."

Setting Up Kanban View for Custom Objects

The Kanban view isn't limited to standard objects. It works with custom objects too — as long as the object has at least one picklist field to serve as the Group By column.

Here's how to set it up:

1. Make sure your custom object has a picklist field that represents the workflow stages or categories you want to track. For example, a "Project" custom object might have a "Project Status" picklist with values like "Planning," "In Progress," "Review," and "Complete."
2. Create a list view for the custom object (or use an existing one).
3. Switch the display to Kanban and select your picklist field as the Group By value.

Some practical examples from real Salesforce implementations:

• Support Cases grouped by Priority (High, Medium, Low) — help desk managers can see the queue at a glance
• Job Applications grouped by Hiring Stage — recruiting teams track candidates visually
• Product Requests grouped by Approval Status — product teams manage incoming feature requests
• Vendor Onboarding grouped by Onboarding Phase — procurement teams track vendor progress

The key requirement: your custom object needs a picklist field with well-defined values. If you're currently using a text field for status tracking, convert it to a picklist first. Without a picklist, the "Group By" dropdown won't have anything to offer.

Kanban View for Opportunities: A Sales Manager's Playbook

Opportunities are where the Kanban view really shines. Here's how to get the most out of it for day-to-day sales management.

Track Deal Movement with Drag-and-Drop

When a rep closes a discovery call and the deal moves to "Proposal," they simply drag the card from the Discovery column to the Proposal column. Salesforce updates the Stage field on the actual Opportunity record in the background. The pipeline summary at the top of each column recalculates instantly.

This is faster than opening the record, clicking "Edit," changing the stage, and saving. For reps managing 30–50 active opportunities, those saved clicks add up to hours per week.

One thing to watch: drag-and-drop triggers any automation tied to the Stage field — workflow rules, process builder flows, approval processes, and validation rules all fire normally. If a validation rule blocks the stage change (say, "Proposal" requires a Quote attached), the drag-and-drop will fail and show an error message. Make sure your reps know what's required at each stage so they don't get surprised.

Spot Stalled Deals with Alert Indicators

The Kanban view adds a small yellow warning icon to any opportunity card that hasn't had activity in 30 days. This is built into Salesforce — you don't need to configure it.

When you see that warning, click the card and choose "New Task" or "New Event" to schedule a follow-up. This simple visual cue is one of the most underused features in Salesforce, and in our experience, it's one of the most impactful for pipeline hygiene.

Sales managers can use the alert indicators during weekly pipeline reviews: "I see four deals in Negotiation with no activity in 30 days. Let's talk about those." It turns a vague check-in into a focused conversation backed by real data.

Inline Editing from the Kanban Card

Click the "Details" icon (it looks like a small panel icon) on any Kanban card to expand a side panel. This panel shows key fields and, for Opportunities, includes Guidance for Success text that admins can configure per stage through Salesforce Path.

Key fields in this panel support inline editing. You can update the Amount, Close Date, or Next Step without leaving the Kanban view. Salesforce validation rules still apply to these edits.

For Unlimited Edition users, there's an extra feature: "Recent Changes" highlighting. When enabled in Opportunity Settings, it marks any changes to Amount or Close Date fields, so managers can see at a glance which deals have been adjusted recently.

Kanban View Limitations and Workarounds

Every tool has boundaries. Knowing the Kanban view's limits helps you work around them or plan alternatives.

If the 200-card limit is a consistent problem, it usually signals that your list view filters need tightening. A well-filtered Kanban board with 40–80 cards is more useful than a crowded one with 200.

For teams that need more flexibility than native Kanban offers — like custom card layouts, multiple swimlanes, or WIP (work-in-progress) limits — Salesforce AppExchange has several third-party Kanban apps that extend the standard functionality.

Kanban View Best Practices for Sales Teams

After helping dozens of sales organizations configure their Salesforce environments, here are the patterns we've seen work best with Kanban:

Keep your stages clean and current. If your Opportunity Stage picklist has 12 values but only 5 are actively used, your Kanban board will have 7 empty columns. Audit your picklist values quarterly and archive or remove stages that no longer reflect your actual sales process.

Set up role-specific Kanban views. A VP of Sales needs a different view than an individual contributor. Create saved list views with filters matching each role: "My Open Opportunities" for reps, "Team Pipeline — Enterprise" for managers, "All Deals Closing This Month" for executives. Each person switches to Kanban on the view that fits their workflow.

Use Kanban for pipeline reviews, not reporting. The Kanban view is a working tool, not a dashboard. For forecasting and trend analysis, use Salesforce Reports and Dashboards. Use Kanban when you need to act on individual deals — reprioritize, update, or follow up.

Pair Kanban with Sales Path. Salesforce Sales Path adds guidance text and key fields for each stage. When combined with Kanban, reps see both the visual pipeline and stage-specific coaching. An admin sets up the Path once; every rep benefits every time they click a card's details panel.

Review stalled deal alerts weekly. Make the 30-day inactivity warnings part of your team's routine. In our experience, teams that review stale deals every Friday reduce their average sales cycle by 15–20% within two quarters — simply because nothing sits idle.

Train new reps on Kanban first. As Salesforce Ben has noted, the visual layout is more intuitive than the table view for someone new to Salesforce. It builds an immediate mental model of the sales process: deals enter on the left, move right, and close at the end. Start new hires here before introducing the more data-dense table and report views.

Frequently Asked Questions

What is the Kanban view in Salesforce?

The Kanban view in Salesforce is a visual display option for list views that shows records as cards organized into columns. Each column represents a picklist value (like Opportunity Stage), and you can drag cards between columns to update records. It's available in Lightning Experience across all Salesforce editions.

How do I enable the Kanban view in Salesforce Lightning?

Navigate to any object's list view (avoid "Recently Viewed"), then click the display icon in the upper-right corner and select "Kanban." Configure your Group By field and optional Summary field, then click Save. You'll need Lightning Experience enabled — Kanban isn't available in Salesforce Classic.

Can I use Kanban view for custom objects in Salesforce?

Yes. The Kanban view works for most standard and custom objects as long as the object has at least one picklist field. Set the picklist field as your "Group By" column in Kanban Settings. Some standard objects like Tasks are exceptions and don't support Kanban view.

What is the card limit in Salesforce Kanban view?

The Salesforce Kanban view displays a maximum of 200 cards. If your list view contains more than 200 records, apply filters to narrow the results before switching to Kanban. This keeps the board usable and focused on the deals that matter most.

How do I change which fields show on Kanban cards?

The Kanban card displays the first four columns from the underlying list view's table layout. To change them, switch to the table view, click the gear icon, select "Select Fields to Display," reorder the columns so your preferred four fields are first, then switch back to Kanban.

Get More Out of Your Salesforce Pipeline with Expert Help

Customizing the Kanban view is just one piece of building a Salesforce environment that actually drives sales performance. At Minuscule Technologies, we help organizations re-engineer their Salesforce orgs for efficiency — from custom implementations and pipeline optimization to ongoing managed services that keep your CRM running smoothly.

Whether you're setting up Kanban views for a new team or untangling a complex multi-object sales process, our 160+ Salesforce engineers have seen it all. Book a free consultation and let's talk about making your Salesforce work harder for your sales team.