> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to group a Kanban by owner or connected record
- URL: https://blog.jestor.com/group-a-kanban-by-owner-or-record/
- Published: 2026-09-16T18:51:31.000Z
- Updated: 2026-09-16T18:51:31.000Z
- Author: Bruno Bannach

Being able to **group a Kanban by owner** rather than by status opens a different way of reading the same work. In **Jestor**, a board can be built from a single option field, a user field, a radio field or a connected record, so the columns can be people, clients or projects instead of stages.

## Why status is not the only useful grouping

Grouping by stage answers where work is. Grouping by person answers who is overloaded. Grouping by client answers where attention is concentrated. These are different management questions, and only one of them is served by the default.

Rebuilding the same data under a different grouping used to mean creating a separate structure.

Groupings worth having:

- By owner, to see workload distribution
- By client or account, to see concentration
- By project, when tasks span several
- By category, when routing matters more than progress

## What each grouping reveals

| Group by         | Columns become       | Question answered               |
| ---------------- | -------------------- | ------------------------------- |
| Single option    | Stages               | Where is the work               |
| User field       | People               | Who is overloaded               |
| Connected record | Clients or projects  | Where is attention concentrated |
| Radio field      | Exclusive categories | How work is distributed by type |

## Step by step to configure it

1. **Open the board** in edit mode.
2. **Find the grouping field setting**, which now accepts more than single option.
3. **Select a user field** to group by person.
4. **Or select a connected field** to group by client or project.
5. **Check the column count**, since grouping by a connected table can produce many.
6. **Create a second board** on the same data rather than switching back and forth.

## Why a second board beats reconfiguring

Grouping is not a setting you want to change twice a day. Building one board grouped by stage and another grouped by owner, both on the same table, gives you two permanent views instead of one that keeps moving. The underlying data is shared, so nothing is duplicated.

- **Four grouping types:** single option, user, radio and connected
- **Same data, different questions:** no duplication required
- **Workload visible:** grouping by person shows distribution immediately
- **Watch the column count:** connected fields can generate many columns

## Frequently Asked Questions

### Can I group a board by the person responsible?

Yes. A user field can be used as the grouping field. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can columns be clients instead of stages?

Yes, by grouping on a connected record field.

### Does creating a second board duplicate my data?

No. Both boards read the same underlying table.

## Video Tutorial: Step by Step

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way, all without code and powered by **AI**. Discover Jestor at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.