How to limit which users appear in a multiple-users field to avoid mistakes

Limiting which users appear in a multiple-users field to avoid mistakes means restricting that field's option list to only the users relevant to that context, instead of showing every user on the account.

When a multiple-users field displays every person registered on the account, it becomes easy to select the wrong person by mistake, especially on accounts with many users from different departments unrelated to that specific record.

What companies are trying to solve:

Reduce the risk of selecting the wrong user in a field with too many options.
Show only the users relevant to that process or department.
Keep multiple-users fields organized even on large accounts.
Avoid visual clutter in selection lists with too many people.

In Jestor, you can now limit which users are available for selection in a multiple-users field, instead of automatically showing every person on the account. This reduces the risk of picking the wrong person when choosing who's responsible for or involved in a record, especially on accounts with a large number of registered users.

Why choose Jestor

Filtered user list, showing only who's relevant to that field.
Lower risk of accidentally selecting the wrong person.
More organized fields even on accounts with many users.
Flexible setup based on each process's needs.

Frequently asked questions

Is this limit mandatory or optional? It's an optional setting, available for those who want to restrict the list. See more at jestor.com.

Does this also affect single-user fields? This feature is aimed at the multiple-users field, which gathers more than one person.

Can I restrict users by department or another criterion? Yes, you can define which users should appear available for selection.

Can this setting be changed later, or is it a one-time thing? It can be reviewed and adjusted whenever the field's configuration needs to change.

Reference video

Also check out Jestor's YouTube channel for more content like this.

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.

What signs show that a company has outgrown manual WhatsApp and needs native automation?

Companies still running things through a personal WhatsApp number or loose group chats eventually notice that the volume of conversations has outgrown their manual control — and that's the point where WhatsApp automation with AI agents in Jestor starts making a real difference in the operation. The symptoms of

How do you migrate a process that currently lives in a spreadsheet into a Jestor app without losing history?

In Jestor, you can upload an existing spreadsheet directly to the platform, and the system already suggests apps and structured processes built on top of the uploaded data, preserving the history that already existed. The fear of losing data during migration Companies that still manage entire processes in spreadsheets — sales,

Native Omie integration vs. contacting Jestor support: when is each one necessary?

In Jestor, the native integration with Omie is set up in a few minutes with an App Key and App Secret, covering approvals, entries, and orchestration across accounts. Contacting Jestor support, at request@jestor.email, is used for specific low-code setup requests, like connecting a template to Omie. When

AI agent that responds on its own vs. one with human verification: how do you set the level of autonomy?

In Jestor, AI agents can operate fully autonomously — responding, filling in fields, and even moving the card on their own — or in human-in-the-loop mode, where a person monitors and validates before the final action is confirmed. The hesitation to give full autonomy right away Companies automating WhatsApp