How to restrict a field that allowed multiple users to accept only one owner?

In Jestor's multiple-users field, you can enable an option that forces the selection of just one owner per record — useful when a process, like a sales opportunity, needs a single clear owner instead of several people responsible at once.

Why does restricting to a single owner prevent confusion in some processes?

Certain processes, like a sales opportunity, work better with a single, clearly defined owner — otherwise it becomes ambiguous who's actually responsible for moving that record forward. Allowing multiple users in those cases can create the sense that "everyone's responsible, so no one is."

How to restrict the field to a single user in Jestor?

Access the settings for the multiple-users field you want to restrict.
Enable the option that forces the selection of just one owner.
Save the change — from then on, selecting a new user replaces the previous one, instead of allowing both at once.
Before that restriction, it's also possible to manually choose which users show up in the selection list, instead of listing everyone registered on the account.

Setting	Behavior
Multiple users (default)	Allows selecting more than one owner
Restricted to one user	Selecting a new user replaces the previous one

Why choose Jestor?

Beyond this restriction, the multiple-users field also gained a searchable selector, making it easier to find the right person even on accounts with hundreds of registered users in Jestor.

Frequently Asked Questions

Can this restriction be undone later? Yes, the field's setting can be reverted to allow multiple users again if needed.

Does this affect records already created before the change? The setting applies to the next selections made in that field.

Can I limit which users show up in the list, beyond restricting the count? Yes, you can manually choose which users are available for selection in that specific field.

Reference video

Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all without code and with AI support.

Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.

How to build an automation roadmap for your company

A good automation roadmap doesn't start by automating everything at once — it starts with a simple starter template, validated with the team, and expands process by process inside a structured BPMS. That's how Jestor recommends starting any implementation. How Do You Build an Automation Roadmap Step

Common mistakes when automating internal processes and how to avoid them

Among the most frequent mistakes automating processes, you'll find automating a poorly mapped process, granting overly broad access to sensitive data, and editing a live workflow without testing it first. Jestor's BPMS, Security, and App Versioning help you avoid exactly these three mistakes. What Are the

How to measure the ROI of a process automation project

Measuring the ROI of process automation requires comparing the tool's cost against the time it saves and the errors it prevents — not just looking at the monthly fee. Jestor's dashboard helps turn this into concrete numbers, comparing before and after automation. How Do You Calculate the

How to identify priority processes to automate first

Priority processes to automate are usually the ones consuming the most team time, generating the most errors, and most affecting the end customer when they go wrong — in that order. Jestor's dashboard and BPMS help you see these three criteria with data, not guesswork. How Do You Prioritize