↑↓ selectEnter openEsc close

    1. Elbuz

    Kanban boards: work with cards instead of lists

    19 min readUpdated

    Elbuz shows tasks, orders, products or customers as cards in columns. Drag a card and the item's status changes: nothing is tracked twice, an order lives in the document list and on the board at once.

    When you need this:

    • Managers move orders through stages: columns follow statuses, so the document list matches the board.
    • A packer takes too many orders: a WIP limit caps the cards in a column.
    • A move must notify someone: an automation sets an assignee, creates a task or sends email.
    • Someone moved a card back: “History” shows who and when.

    Where to start: “Organizer” → “Boards” → new board, the “Item Type” field.

    What a board can do

    What to build a board on: kanban or funnel

    The first thing Elbuz asks when you create a board is which type of items it works with. This is not a cosmetic choice: it decides what can become a card at all.

    The field in the board form is called “Item Type”, and it has fifteen options, listed alphabetically: “Articles”, “Categories”, “Contacts”, “Documents”, “Employees”, “Finance”, “Manufacturers”, “Newsletter”, “Notes”, “Other”, “Products”, “Projects”, “Stocks”, “Support requests” and “Tasks”.

    • “Documents” means orders, invoices and other documents.
    • “Contacts” means customers and other contacts: there is no separate “Customers” option in the list.
    • Next to it is the “Board Type” field: “Kanban” or “Funnel” (how they differ).

    So a board can serve not only a department's work but also, say, filling in product cards: columns “No description” → “Description written” → “Photos added” → “Ready for export”.

    “Item Type” and “Board Type” (Kanban or Funnel) are set once, when the board is created, and can't be changed later: both fields are disabled in the board edit form. The cards simply wouldn't know what they had become. If you picked the wrong type, or a kanban needs to become a funnel, create a new board.

    A funnel is a different mode

    Besides kanban, a board can be a funnel. The difference isn't in the look: funnel columns get a probability in percent and terminal stage marks, “Won” and “Lost”. Stage weight drives the weighted forecast of deal amounts, and terminal stages close the deal.

    This is a separate topic with its own “Pipelines and stages” window. Here we only note that kanban and funnel are set up in the same place, and you shouldn't mix them up: use a kanban for team work and a funnel for sales.

    How items get onto the board and into a column

    You don't add cards to a board by hand: they appear by themselves when an item matches the board conditions. Conditions are set in a builder: field, operator, value, and you can combine several with “and” / “or”. For example, an “Orders in progress” board takes documents whose type is “Customer order” and whose status is neither “Done” nor “Canceled”.

    For a board with “Item Type” set to “Documents”, the builder's field list is the columns of the document list: all of them from the column settings, not only the visible ones.

    They include “Document type”, “Status”, “Payment status”, “Payment type”, “Delivery method”, “Delivery status”, “Source warehouse”, “Recipient company”, “Contact”, “Store”, “Source: name”, “Employee”, “Tags”, dates (“Date added”, “Pay by” and others) and numbers: “Amount”, “Paid”, “Delivery price”.

    Statuses, payment type, delivery method, document type, warehouses and companies are picked from a directory list; numbers have “less than”, “greater than” and “between”. Additional document fields are in the list too, marked as attributes.

    Example, a board of large orders: “Document type” equals “Customer order” and “Amount” is greater than 10000. The amount is compared as stored in the document, in its currency.

    Next, Elbuz has to decide which column gets the card. There are three ways, applied in this order:

    1. Column conditions. Each column can have its own conditions, in the same builder. If several columns match, the card goes to the last of them in column order.
    2. Item status. If no conditions are set, Elbuz looks for a column linked to the item's status. This way the board repeats your process automatically: document statuses become columns.
    3. First column. If neither of the above works, the card goes to the leftmost column.
    Three rules in a row, each one used only when the previous one didn't work. The bottom branch is the very reason why “everything landed in the first column”
    NoYesYesNoYesNoAn item in Elbuz changedDoes it matchthe board conditions?No card.A board without any conditiongets nothingDo columns have their ownconditions, and do they match?The card goes to the lastmatching column in orderIs there a column linkedto this item's status?The card goes to the columnof this statusThe card landsin the leftmost column
    • Action or result
    • Decision: the path depends on the answer

    The simplest working setup is to link columns to statuses. Then the board makes nothing up: a manager drags a card, the document status changes, and the document list and the board show the same thing.

    A board without a single condition gets no cards: Elbuz skips such boards. An empty board a day after creation almost always means exactly this.

    How to set up columns: color, WIP limit and locking

    You add a column with “Add a column” and edit it with “Edit column”. Besides the name and color, a column has two properties worth understanding.

    WIP limit is how many cards a column may hold at once; zero means “no limit”. Once it's reached, you can't drag cards into that column.

    This is the point of kanban, not red tape: the limit shows where work piles up. An “In progress” column with a limit of 3 per manager honestly shows when someone took on seven things at once.

    Locking a column stops cards from being moved into it: by dragging, a bulk action or picking the column in the card. Elbuz then says: “The column is locked! Moving cards is prohibited.” Taking a card out still works. Use it for terminal columns like “Archive”, where cards arrive automatically by status or conditions.

    What happens after you drop a card. A locked column doesn't accept it, and a reached limit or a role without edit rights sends it back. The item status changes only when the column is linked to a status
    YesNoYesNoNoYesYesNoYesNoA card is draggedto another columnIs the column locked?The column doesn't accept the cardHas the column reachedits WIP limit?Red message.The board reloads,the card returns to its placeIs your board roleeditor or owner?The card moves.Board history recordsfrom where and to whereIs the column linkedto an item status?The item getsthe column's statusAre there active automationsfor this transition?Each one's action runs.Board history recordsthe automation numberDone
    • Action or result
    • Decision: the path depends on the answer

    When you delete a column that has cards, Elbuz asks separately, with a number: “There are N cards in the column. They will be deleted. Continue?”. Read this message carefully: it's not about the column, it's about the cards in it.

    Where colors come from: the “Colors” window

    Colors window with the palette: swatches, activity, name, code, order
    1Swatch
    2Activity
    3Name
    1. Swatch column — the color rendered from its HEX code.
    2. Activity — a disabled color disappears from the selection lists.
    3. Name — how the color is labeled in the board form.

    The board color (the “Color” field in the board form) and a column color in that form's column list (the “Color Selector” button) come from a palette, the “Colors” directory. The “Editing a column” window (the “Edit column” button) on the board has its own set: six fixed colors the directory doesn't affect.

    The “Colors” window has no menu item. You open it with a shortcut: right-click an empty spot on the desktop → “Add shortcut” → “Colors”. If that line isn't there, the window is closed to your department, and a manager can open it in department permissions.

    The window shows the palette grid: color sample, “Activity”, “Name”, “Description”, “Code”, “Order”. Name, description, activity and order are edited by double-clicking a cell. Turning “Activity” off removes the color from pick lists, while boards and columns that already use it keep their color.

    You can't add your own color with a HEX code. The “Add” button creates a row with no color and no code, and neither a HEX code nor a code entered in the grid is saved. The palette has thirty ready colors; pick the closest one and give it your own name.

    What dragging does to an order

    When a board is built on documents, you drag a card to move an order forward. Here is what changes and what doesn't.

    • If the target column is linked to a status, the document gets that status. Elbuz records the time of the status change and adds a status-change entry to the document history.
    • If the column has no status (defined by conditions only), nothing happens to the document: only the card's position on the board changes.
    • Dragging doesn't touch posting. A posted document stays posted, an unposted one stays unposted. The status changes in both cases: you can drag a posted order too.
    • Stock levels don't move. Only the “Post” button on a stock document, such as a sales invoice, changes stock. Moving an order to “Completed” or “Issued” on the board doesn't write the goods off.

    Reservation is the only stock-related thing dragging can affect. Elbuz recalculates it for the order's products only when three conditions are met: the document is posted, its type has “Reserves stock” turned on (as a customer order does), and the working scheme for documents tracks stock. Then:

    • if the card is dragged to a column with a closing status (in the standard directory these are “Completed”, “Done”, “Issued”, “Canceled”, “Rejected”, “Voided”, “Returned”, “Product return”, “Canceled return”, “Overdue” (Прострочено), “Not relevant”, “Failed”), the order's reservation is released;
    • if the card is moved back to a column with any other status, the reservation returns;
    • the “Paid” status doesn't release the reservation: a paid but unshipped order still holds the goods;
    • only the unshipped quantity is reserved: what a posted sales invoice has already written off is not reserved again.

    If any of the three conditions isn't met (the order isn't posted, the type has no “Reserves stock”, or the scheme doesn't track stock), dragging changes only the status, and the reservation stays as it was.

    The “Update an item field” automation writes the value straight into the document. If it changes the document status, the reservation isn't recalculated and no entry appears in the document history, unlike dragging to a column linked to a status. To change an order's status, link the column to the status instead of setting up an automation.

    A bulk move (select cards and pick a column) changes statuses and runs board automations just like dragging cards one by one.

    A bulk move skips any card whose target column has reached its WIP limit, as well as cards from boards where your role is below editor. It moves none into a locked column.

    Elbuz shows “Done” in each of these cases, so you see which cards actually moved only on the refreshed board.

    How to find cards and change several at once

    Besides the item itself, a card has its own work fields: assignee, deadline, priority (low, medium, high, urgent) and amount, which matters on boards about money.

    Above the board is a panel that helps once you have more than a hundred cards:

    • Filters: the “Filters” button above the board opens a row with “Search...” (by card name, item , not document number, and customer), the “All users” assignee list, the “All priorities” list (Low, Medium, High, Urgent), “Date from” and “Date until” (card creation date), “Amount from” and “Amount up to”. “Clear” resets everything; the counter “Cards found: N” shows the result.
    • Sorting inside a column: newest first, nearest deadline, high priority, highest amount or manual order.
    • Bulk actions move and edit cards in bulk: select several cards with checkboxes (or “Select all”) and in the “Bulk actions” menu choose “Move to...”, “Assign to...”, “Set a deadline” or delete. Before moving, Elbuz asks “Move N cards?”. This is about board cards; bulk changing of product categories in the catalog is a separate feature.

    Only my urgent cards. Click “Filters”, choose yourself in the “All users” list and “Urgent” in the “All priorities” list.

    The user here is the card's assignee, so the cards left are those assigned to you. The board has no ready filters like “Assigned to me”, “Overdue” or “Today”, and you pick one priority only: you can't show “High” and “Urgent” together. To get the nearest deadlines at the top of a column, set sorting to “Nearest deadline”.

    How many cards a board shows

    A board loads at most 50 columns and at most 50 cards per column, the first ones in the column's card order. If a column has more cards, the rest don't appear on screen, although they are on the board and their items' statuses don't change.

    This has consequences worth knowing:

    • the counter and amount in the column header count only the loaded cards, so at most 50;
    • filters and search on the panel above the board look only among loaded cards: a card outside the first 50 won't be found;
    • the WIP limit is checked at the moment of dragging against all cards in the column, including those not loaded on screen.

    If a column regularly overflows, split it: narrow the board conditions or spread items across several columns with separate statuses or conditions.

    Who can do what on a board and where to see who moved a card

    Everyone with rights to the “Boards” window sees the board; roles decide what a person can do with cards and columns. The “Access” button opens the list of users with their roles:

    RoleWhat they can do
    Ownereverything, including board settings and granting access
    Editorwork with cards: create, move, change
    Commenterthe same as Viewer: view only
    Viewerview only

    Board roles apply on top of general window access rights: a person without rights to the “Boards” window won't see the board even with the owner role. General rights are covered in a separate article on access rights.

    Change history: who moved a card or changed the assignee, and when

    Where: above the board, the “History” button, a log of operations with this board's cards. It shows who did what and when: card created, card updated, card moved between columns, assignee changed, card deleted. For a move, it shows where the card came from and where it went.

    This is most useful in two cases: when you need to find out who dragged a card back and when, and when a card disappeared, since deletion leaves a trace too.

    If the board holds organizer records, status changes made by dragging and edits made by automations are also written to the record's own change history, which you see in the record form, in the “Change history” section.

    How to set up an action on a card move

    A board can react to card moves. “Add automation” opens a simple two-part rule.

    The trigger is always the same: a card move. You narrow it with two fields, “From column” and “To column”. “To column” is required, and “From column” can be left as “Any column”. So the rule fires on a specific transition or on any arrival in the chosen column.

    The rule runs when a card is moved (dragged or by a bulk action) into another column. It doesn't run when cards are reordered inside a column, or when a card lands in a column by itself through status or conditions. Each run leaves an entry with the automation number in the board history.

    The action is one of four:

    ActionWhat it does
    Set assigneefor a document, makes the chosen user the assignee; for an organizer task or project, adds them to the record's assignees, so they see the record and get its reminders
    Send email notificationsends an email using the template chosen in “Email template” to the address in “Recipient's email”; without a template no email goes out, as there is no text to take
    Create a linked taskcreates a task with your name and description
    Update an item fieldwrites a value to a field of the item itself, not the card

    An automation email is sent like any other template email: the address from the automation overrides the one in the template, and record macros work in the text. A mail failure doesn't stop the card move, and the board's “History” keeps an entry that the automation ran.

    Email the logistics manager when a card is moved to the “Shipped” column. There are three ways:

    • Board automation, the shortest: “To column” is “Shipped”, action “Send email notification”, “Email template” is a mail template created in advance, and “Recipient's email” is the logistics manager's address.
    • Trigger, if the email must go out on any status change (from the document card, an import), not only from the board: event “Document: update”, condition document status “Shipped”, command “Send mail”; put the logistics manager's address in the template's “Recipient's E-Mail” field. Dragging a card into a status-linked column changes the document status, so the trigger fires then too.
    • No email, if the logistics manager only needs to see the work in the organizer: the “Set assignee” or “Create a linked task” action.

    “Update an item field” is the most powerful and dangerous action: it changes a document, product, contact or organizer record. In “Field name”, enter the technical name of the item's field as stored in the database. If the item has no such field, the action doesn't run and nothing changes.

    It doesn't change a posted document either, only an unposted one. Test it on one card before leaving the rule running.

    “Update an item field” doesn't check what's currently in the field. If you corrected the field by hand and the card is later dragged into the same column again, the rule writes its value again and your edit is lost.

    To keep a manual value, turn the rule off with the switch in the automation form, or don't move the card back to that column. For tasks, projects and notes, the overwrite shows in the record's change history; for a document, product or contact, it isn't written to history.

    Board automations are not triggers, which work across all of Elbuz. Board rules know only one event, a card move, and live within their board. For a reaction to an event anywhere in the system, use triggers.

    Scenarios

    Orders move through statuses, and the document list shows the same

    Task: managers handle customer orders on a board, and the status in the document list must match the column.

    What to set up: create a board with “Item Type” “Documents”, add a board condition on document type, and in the form's “Stages (workflow)” table choose an “Item Status (Link)” for each column.

    Board form for Orders with the Stages (workflow) table
    1Item status (link)
    2Status picker arrow
    3Limit (WIP)
    1. Item status (link) — the status this column is tied to; dragging a card here changes the document status.
    2. Arrow button — picks the status from the reference list.
    3. Limit (WIP) — 0 means no limit.

    Result: a new order lands in its status column. Drag a card and the document gets the column's status, with the change time recorded and a document history entry.

    What won't happen: the document won't be posted or unposted, and goods won't be written off; for the reservation, see what dragging does to an order.

    Prom and Rozetka marketplace orders on a kanban board: statuses new, picked, shipped, delivery

    Task: move marketplace orders through statuses on a board, from new to delivery.

    What to set up: create a board with “Board Type” “Kanban” and “Item Type” “Documents”. The board condition is document type “Customer order”. Add columns with “Add a column” (“New”, “Picked”, “Shipped”) and in the “Stages (workflow)” table link each to its status with “Item Status (Link)”.

    Result: an order imported from Prom or Rozetka becomes an Elbuz document and lands in its status column by itself. Drag a card and the document status in Elbuz changes: it's the same record as in the document list.

    What won't happen: the board sends nothing to the marketplace; it only changes the document status in Elbuz.

    No more than three orders in progress at once

    Task: a packer shouldn't take new orders before finishing the current ones.

    What to set up: in the “Packing” column, open “Edit column” and set “WIP limit (0 = no limit)” to 3.

    Result: you can't drag a fourth card into this column: Elbuz shows “The column card limit has been reached (3)”, reloads the board and returns the card. The limit counts all cards in the column, not only those on screen. Zero removes the limit.

    An order in “Packing” gets an assignee automatically

    Task: as soon as an order reaches the packing column, the warehouse keeper must become its assignee.

    What to set up: “Add automation”, in “To column” choose “Packing”, leave “Any column” in “From column”, set “Action type” to “Set assignee”, and in “Assign a user” choose the warehouse keeper.

    Result: whenever a card is moved here, singly or in bulk, the document gets the warehouse keeper as assignee, and the board history gets an entry with the automation number.

    On a task or project board, the same action adds the person to the record's assignees. What won't happen: the rule won't fire on reordering inside the column, or while it's switched off in the automation form.

    Completed tasks don't go back

    Task: on a task board, a card that reached “Done” mustn't accidentally return to work.

    What to set up: in the “Stages (workflow)” table, link the “Done” column to the completed task status with “Item Status (Link)”, and in “Edit column” turn on “Lock the column (prevent moving cards)”.

    Result: a lock appears in the column header, cards in it can't be picked up with the mouse, and the column accepts no dragged cards.

    A card gets there by itself: when the assignee saves the task with the completed status, it moves to “Done”. What won't happen: the lock doesn't stop anyone from changing the task's status in the form; the card then moves to the new status's column, or to the board's first column if there is none.

    What to do when a board behaves unexpectedly

    What you seeWhyWhat to do
    The board is empty, though items existthe board has no conditions, and Elbuz skips such boardsopen the board settings and add a filter condition
    All cards landed in the first columncolumns have no conditions, and no statuses are linked to themlink columns to item statuses or set column conditions
    A card can't be draggedeither the column is locked or the target column has reached its WIP limitcheck the message: for both locking and a reached limit, Elbuz shows a red message (with a number for the limit) and reloads the board, returning the card to its place
    A colleague can't see the boardthey have no rights to the “Boards” windowcheck the user's group permissions for the “Boards” window
    A card disappeared from the board by itselfthe item no longer matches the board conditions, for example its status changedthis is normal; if you still need the card, widen the conditions
    I deleted a column and the cards are gonedeleting a column deletes its cards, and Elbuz warns about this with a numbermove the cards to another column before deleting

    FAQ

    How do I add a card manually?

    Cards appear by themselves, based on the board conditions. If an item didn't get onto the board, it didn't match the conditions: change the conditions rather than adding the card separately.

    I'm creating a board: what should I pick in “Item Type” to manage customers?

    Choose “Contacts”: that's what the list calls customers, suppliers and other contacts; there is no “Customers” option there. The type is set once when the board is created and can't be changed later.

    Can I change the board type from kanban to funnel after creation?

    No. “Board Type” and “Item Type” are chosen at creation and are disabled in the edit form. Create a new board with the “Funnel” type (what to build a board on).

    Can I restore a deleted card?

    The card itself, no, but the change history keeps a deletion entry showing who did it and when. The item itself doesn't go anywhere; it stays in its own list.

    How do I select several cards and move them to another column together?

    Select the cards with checkboxes (or “Select all”), open “Bulk actions” → “Move to...” and choose a column. Cards whose target column has reached its WIP limit are skipped, and none move into a locked column (bulk move).

    There are lots of cards on the board: how do I filter only my urgent ones?

    “Filters” → choose yourself in the “All users” list and “Urgent” in “All priorities”. Filtering goes by the card's assignee; there are no ready filters like “Assigned to me” or “Overdue” (board filters).

    How do I set up an automatic email to the logistics manager when an order is moved to the “Shipped” column?

    Add a board automation: “To column” is “Shipped”, action “Send email notification”, a mail template and the logistics manager's address. If the email is needed on any status change, not only from the board, use a trigger (automations).

    Where can I add my own HEX color for boards?

    Nowhere: the “Colors” directory doesn't save your own HEX code. You can rename a ready color, change its order or turn it off (the “Colors” window).

    Where it is and who has access

    Menu
    Organizer → Boards
    Create
    the add button in the board list
    Open a board
    the eye icon “Open” in the list row
    Access right
    the “Boards” window in group permissions; actions on the board depend on the board role
    Kanban board with a row of columns and a filter panel on top
    1Column
    2Filter panel
    1. Column — cards move from left to right as the work progresses.
    2. Filter panel — on a board with hundreds of cards, use it to filter and sort them.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free