List View Kanban
Kanban-style clarity. Grid-based precision.
Give your Salesforce List Views a smarter layer - kanban-style segmentation, grid-level precision, and zero disruption to how you work.
Kanban clarity meets list view control.
Picklist-style filtering, zero disruption.
Unlike traditional Kanban boards that rely on drag-and-drop movement, List View Kanban offers a different approach - click a picklist value in the kanban bar to instantly filter your grid. It’s fast, clean, and purpose-built for when you need focused segmentation without manual card movement.
- Maintain grid precision with kanban-inspired segmentation
- Avoid accidental updates with a click-to-filter experience
Add muscle to your List View.
Start with any existing Salesforce List View - then supercharge it with GridMate functionality: advanced filters, search, pagination, and customizable columns.
- Works with any object that supports a List View
- Retain list view structure while adding powerful filtering and display controls
Define columns with labels that speak your team's language.
Admins can choose any field to define kanban columns. Add custom labels to match how your teams think and work.
- Define kanban structure with any picklist field
- Replace default picklist values with clear, team-friendly labels
Scale up without slowing down.
Support up to 2,000 records per view and display up to 80 columns. This is filtering at scale, made simple.
- Handle large data volumes with consistent performance
- Display far more fields and rows than standard Salesforce Kanban
See the List View Kanban
in action!
Make the leap from standard to standout.
Bring the best of List Views and Kanban together - enhanced filtering, flexible structure, and smarter segmentation in a single, powerful component.
Frequently Asked Questions
If I install the GridMate package for all users, do I need to assign GridMate permission set(s) for each new user going forward?
Yes. The GridMate permission sets grant access to Apex classes, Visualforce pages, objects, and other components. When you first install the package and choose “Install for All Users,” these settings are automatically applied to existing users.
However, when new users are added later, you must manually assign the appropriate permission set. GridMate access is managed entirely through permissions, so assigning the permission set is highly recommended.
GridMate User
This is the base permission set required for any user who needs access to GridMate components (except User Grids). It includes object and field access, as well as Apex classes. Each GridMate user should have this permission.
GridMate Advanced User
This permission set is used to grant access to User Grids. Its purpose is for advanced users who require permission to create their own grids.
GridMate Admin
This permission set is used for Business Analysts to have access to the config wizard, inline configuration and SOQL Preview buttons. It's applicable only if they don't have access to the setup.
GridMate Cockpit User
The GridMate Cockpit User permission set allows users to manage all GridMate settings in one place - including grid-level field access, action controls, and component visibility. It grants access to the Cockpit tab and its features.
Does GridMate support inline editing for multiple record types?
Yes. GridMate supports inline editing for multiple record types simultaneously. Dependent picklists are respected as well.
Can the record Id be passed to a GridMate component on Experience Cloud?
Yes. GridMate supports this functionality. You can define the recordId property using the syntax "{!recordId}".
Is there a partner agreement?
Yes, it’s a straightforward agreement that outlines the roles, expectations, and rewards of our affiliate partnership. It helps keep everything clear and aligned, while protecting everyone’s interests.
Should we grant a GridMate license to every user?
No, GridMate licenses should be granted only to relevant users. GridMate components can be combined with standard components using visibility conditions in the Lightning App Builder.
We recommend creating a custom permission set, assigning it to licensed users, and then using this permission to control component visibility in the Lightning App Builder. See below:
Got any more
questions?
