Switch to Kanban Board
Add a kanban board view alongside your existing table view so users can drag records between status columns without leaving the app. This template keeps the table as default and adds a switcher for faster triage and workflow tracking.
Trusted by frontline teams 15 years of frontline software
Built for: Facilities Management · Manufacturing · Healthcare Operations · Education · Property Management
Overview
This template adds a kanban board view to an existing record type while preserving the current table view as the default. It is designed for apps where each record already has a status or stage field and users need a faster way to see work in progress, move items between stages, and spot bottlenecks without opening every row.
Use it when your workflow is stage-based and the team benefits from a visual board for triage, coordination, or daily follow-up. The template updates the record schema to declare the board view, adds a view switcher in the index screen, creates the board partial, and wires in the Stimulus controller that supports drag-and-drop. That makes it a good fit for maintenance logs, incident follow-up, booking requests, or small operational queues.
Do not use it when records do not have a stable lifecycle, when users need heavy filtering and column-level analysis more than movement between stages, or when the board would hide important detail that only the table can show. It is also a poor fit if the workflow has many statuses that would create too many columns. The value here is a clean, reusable board layered onto an existing list, not a replacement for every view in the app.
How to use this template
- 1. Confirm that the main record type already has a status or stage select field that can serve as the board column source.
- 2. Update the record schema so the board view is declared with that field as the column_field and the table view remains the default.
- 3. Add the view switcher partial to the index view so users can move between table and board without leaving the record list.
- 4. Create the board view partial and map each status value to a visible column with cards that show the key fields needed for quick scanning.
- 5. Add the board Stimulus controller so drag-and-drop updates the record's status or stage field and refreshes the board state correctly.
- 6. Test the workflow with sample data, then review empty columns, status labels, and permission rules before rolling it out.
Best practices
- Keep the number of board columns small enough that a user can scan the full workflow at a glance.
- Use a single, authoritative status field for the board so the table view and board view never drift apart.
- Show only the fields needed for triage on each card, and leave deeper detail for the record detail screen.
- Photograph or attach evidence at the record level when a move between stages depends on proof, such as a repair or incident follow-up.
- Define clear permission rules for who can drag records between columns and who can only view the board.
- Make empty states explicit so a blank column reads as a valid workflow state, not a rendering problem.
- Keep status names short and operational, because long labels make the board harder to scan and drag accurately.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this template actually add to my app?
It adds a kanban board view to the main record type, using an existing status or stage select field as the column source. The template also updates the record schema, adds a view switcher in the index view, and includes the board partial plus the Stimulus controller for drag-and-drop. Your existing table view stays in place as the default.
What kind of record types is this best for?
It works best for records that move through clear stages, such as maintenance requests, equipment repairs, visitor approvals, incident follow-ups, room bookings, or inventory replenishment tasks. If your records do not have a meaningful status or stage field, the board view will feel forced. Use it when the team needs a visual workflow, not just a list.
Do I need to change my data model before using it?
You need a status or stage select field that can drive the board columns. The template expects the record schema to declare that field as the board's column_field. If your app already has a lifecycle field, this is usually a small edit rather than a redesign.
Who should use the board view versus the table view?
The board view is useful for coordinators, supervisors, and frontline leads who need to move items across stages quickly. The table view is better for scanning many fields at once, sorting, and doing detailed review. Keeping both lets different roles work the way they need to.
How does drag-and-drop behave in this template?
The board controller handles moving a record from one column to another and updating its status or stage field. That means the board is not just visual; it changes the underlying record state. If your workflow has restricted transitions, you should validate those rules before enabling free movement.
What are the common mistakes when adding a kanban board?
A common mistake is using too many statuses, which makes the board hard to scan. Another is leaving the table and board out of sync, so users are unsure which view is authoritative. It is also easy to forget empty-state handling, which makes unused columns look broken instead of intentional.
Can I customize the columns and labels?
Yes. You can rename the status values, adjust the order of columns, and tailor the board cards to show the fields that matter most. The template is meant to be a starting point, so you can match the board to your workflow rather than forcing your workflow to match the board.
How should I roll this out to an existing team?
Start with one record type and one workflow owner, then confirm the status field values before training users. Keep the table view available during rollout so people can compare both views while they adapt. Once the board is stable, you can decide whether it should become the preferred view for daily work.
Related templates
Ready to use this template?
Get started with MangoApps and use Switch to Kanban Board with your team — pricing built for small business.
