Kanban for M‑Files: who has what, by when

CtrlPortals puts the objects from a view or search on a kanban board, each card with its people and its deadline. Move a card to another column and the object changes with it. Any M‑Files edition will do, in M‑Files Cloud or on-premise.

A kanban board drawn by CtrlPortals, called Open vacancies, showing its Interviews and Offer columns. Each vacancy is a card with its number of openings, the initials of the people on it and the date its next step is due: two dates in red because they have passed, two in orange because they are close. The openings are added up under each column, a legend names the departments the cards are coloured by, and a narrow strip on the right holds the two columns hidden from this board.

Who has it and when it is due, on every card

A card carries what people look for before they act on it. Read the board column by column and the state of the work is plain.

Faces you recognise

The people an object is assigned to sit at the foot of its card, with their employee picture or their initials in their own colour.

Dates that warn you

A deadline shows in orange when it is close and in red when it is missed. Late work is the first thing anyone sees.

The fields you choose

Under the title, a card shows the few fields that matter for this work, such as the openings, the customer or the hours.

Colours with a meaning

Cards can be coloured by a field, say the department or the priority, and a legend under the board names each colour.

The whole Open vacancies board: Advertised, Interviews, Offer and Filled columns, each with its number of cards and the sum of the openings under it. Every vacancy card shows its openings, the initials of the people on it and its next date, in red when the date has passed and orange when it is close; the cards in Filled keep a plain date. Buttons above the board show the same vacancies as a list, on a calendar or as a gantt chart.

Columns from your workflow, or from any field

Most boards follow a workflow, with a column for each state. A board can just as well be built on another field, such as the person who handles each case or its priority.

A CtrlPortals board called Customer cases with a column for each of three people, Jonas Lind, Mette Kjaer and Peter Dahl. Each case card shows its customer, its hours and the date a reply is due, in red for yesterday and in orange for today and Monday, and the cards are coloured by priority. The hours are added up under each person's column.

Hand a case over with a drag

On a board by person, every column is someone on the team. When one of them is away, their cases go to a colleague with a drag. Each case then names its new owner in M‑Files.

  • On a workflow board, a card only goes to the states its workflow allows from where it stands.
  • A total under each column sums a number such as the hours, the openings or the value.
  • A right-click on a card offers to open the object, or to filter the board by any value it holds.

Watch a board built around your own work

Wherever work waits for the next person

Anything in the vault that moves through stages can be a card. Three examples from different corners of a company:

Vacancies on their way to a signed offer

A hiring manager follows every open position from advert through interviews to offer. The interviewers are on each card, a red date shows where a candidate is waiting for an answer, and each column counts the positions still to fill.

New suppliers, from questionnaire to approval

A purchasing lead keeps each supplier under review on a board laid out by the steps of its approval workflow. A supplier reaches Approved only when the workflow allows it. The yearly spend waiting on a decision is totalled under each step.

Customer cases, by who handles them

A service manager lays the open cases out by the person handling each one. Before a holiday, cases are handed to colleagues with a drag, and the orange and red dates show which replies are due first.

The same cards as a plan, a list or a calendar

The board is only one way to look at these objects. A click turns it into a plan, a list or a calendar, and a card you picked stays picked.

  • A list for changing many at once — Change values right in the list, and send all of it to Excel with a single button.
  • On a dashboard or a portal — Put the board on a dashboard next to the team's figures, or on a single object's portal: a customer's page, for instance, listing that customer's open cases.

Arranged the way you work

Your administrator decides what the board shows. Each person can then shape it for their own day, without changing it for anyone else.

  • Hide the columns you skip — A stage you never act on can be hidden from your board and brought back whenever you want it.
  • Your own grouping — Regroup the cards by another field, such as the person or the priority, when a different view of the same work helps.
  • Only the cards you want — Search and filters narrow the board to your own cards, one customer or one department.

Saved on the object, under your rights

Every card is read from the vault. Every move lands on the object itself, in the name of the person who made it.

  • Within each person's rights — Everyone sees and moves cards under their own M‑Files permissions, and no further.
  • Checked before it saves — If a colleague changed the same object after the board opened, both versions are shown, and you choose which one stays.
  • Built in M‑Files Admin — The board starts from a view or search. The administrator then picks the field for the columns, what a card shows, the colours and the totals.

What it needs to run

  • Any M‑Files edition, in M‑Files Cloud or on-premise, with M‑Files 25.1 or later on the server and in the clients.
  • CtrlPortals, which includes the board, and M‑Files licences for the people who use it.
  • M‑Files Web and both M‑Files desktop clients, new and classic.
  • A view or search that finds the objects, and a field for the columns: the workflow state or any other property.

The CtrlPortals documentation explains how the columns, the card fields and the totals are set up.

Pick one queue and see it as a board

Name a queue your team keeps in a view or a spreadsheet today, such as vacancies, suppliers or customer cases, and we'll show it to you as a board in M‑Files.

What people ask about kanban in M‑Files

Does the board have to follow a workflow?
No. Any field the objects carry can supply the columns: the person responsible, a priority, a customer or a stage. If the columns are the workflow's states, a card goes only to the states its workflow allows from where it stands.
What changes in M‑Files when a card moves?
The object does. It moves to the new workflow state, or takes the new column's value in the field the board is built on. The change is saved under the name of whoever moved the card, within their M‑Files rights, once CtrlPortals has checked that nobody else changed the object after the board was opened.
Which objects end up on the board?
Whatever the M‑Files view or search behind it finds, so a view your team already keeps can become a board. Documents and every other kind of object can be cards.
Can each person narrow the board to their own work?
Yes. The search box and the filters leave only the cards you want, for example yours or one customer's, and a card's own menu filters the board by any value on that card. Each person can also hide the columns they do not need, on their own board only.
Does the board copy data out of M‑Files?
No. The cards come straight from the vault, with no reporting server or separate database in between, so they show what M‑Files holds when the board opens.
Is the kanban board a separate product?
No. The board is one of the things CtrlPortals adds to M‑Files, beside dashboards, portals, forms, gantt charts and calendars. Licences are per normalised M‑Files user, and there is a 30-day trial. Let us know the number of users, and we'll answer the same working day.