> ## 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 Use User Fields for Ownership and Routing
- URL: https://blog.jestor.com/use-user-fields-for-ownership/
- Published: 2026-09-17T22:37:46.000Z
- Updated: 2026-09-17T22:37:46.000Z
- Author: Bruno Bannach

To **use user fields for ownership**, treat them as structure rather than as labels. A user field drives assignment, routing, notification, and often what a person can see.

## What a user field enables

More than recording who is responsible.

- Routing an approval to the right person automatically
- Scoping permissions so people see their own records
- Building a board with people as columns
- Notifying the responsible person on a change
- Reassigning cover when someone is away

## Single or multiple users

| Situation                  | Field                                                |
| -------------------------- | ---------------------------------------------------- |
| **One responsible person** | Single user — accountability is unambiguous          |
| **Approval cover needed**  | Multiple users — either can act, both recorded       |
| **Shared visibility only** | Permissions, not a user field                        |
| **Team assignment**        | A role or team field rather than listing individuals |

## How to configure it in Jestor

1. Use a single-user field in **Jestor** where one person is accountable.
2. Use a multiple-users field on **cost center** records, so approval cover exists.
3. Scope permissions by the user field so people see the records they own.
4. Build a board from the user field where a per-person view helps.
5. Reassign the field temporarily when someone is away, and reverse it on return.

## Why choose Jestor for ownership structures?

**Jestor** can build a **Kanban** from a user field as well as from a status field, which means a board of who is doing what requires no additional structure.

Because approval routing reads the cost centre's responsible users, cover is a data change on one record rather than a reconfiguration of the process.

## Frequently Asked Questions

### When should a field allow several users?

Where cover is needed, such as approval. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can a board be built from a user field?

Yes.

### How do I arrange cover?

Reassign the responsible users temporarily.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

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://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.