Assign a Person Through a monday.com Form (People Column)
Published on September 26, 2026
You want a form submission to land on a board with an owner already attached, not just a pile of unassigned items your team has to triage by hand. That means putting a People question on the form itself, so the respondent (or an automation right after) sets who is responsible.
The catch is that monday.com’s own People column carries account-visibility rules that most other question types don’t, and those rules change depending on whether your form is public or restricted to signed-in account members. Get this wrong and you either expose more of your team roster than you meant to, or the field silently doesn’t show up for external respondents.
Quick answer
- monday.com’s People Column support article states the People question in WorkForms is “only available if the form is restricted to account members only” by default.
- A public WorkForm can still show a People question, but only after an admin enables Administration > Customization > Features > Allow public account forms to use account data — which exposes account member names, titles, and photos to external submitters.
- FormFlow’s field library lists People (“select from monday.com users”) as a standard field alongside every other column type, with no separate public/internal restriction documented.
- Install FormFlow and check how the People field behaves on your own public form before relying on it for external respondents — see the confirm-first note below.
How WorkForms Handles People on Public Forms
The account-visibility rule exists because a People question means asking a respondent to pick from a list of your account’s users — full names and often photos. monday.com treats that as account data, not form data, so it applies the same access rule it uses elsewhere: an internal-only form (restricted to account members) can show the full list, but a public form needs explicit opt-in.
That opt-in is one account-wide toggle, not a per-form setting: Administration > Customization > Features > Allow public account forms to use account data. Once an admin enables it, People questions become visible on public WorkForms too, and dropdown options are still scoped to the board or workspace’s members when the board itself is private or shareable rather than fully public.
Two things worth knowing before you flip that switch:
- It applies to every public form on the account, not just the one you’re building. Enabling People on one intake form exposes account member data on all of them.
- Anyone who fills out any public form afterward can see the names, titles, and (if set) photos of the people that dropdown lists, whether or not they otherwise have access to your account.
For an internal-only ticket or request form — HR intake, IT tickets, anything already restricted to signed-in teammates — none of this applies. The WorkForms settings and permissions article covers the account-member restriction directly, and People works there without the extra toggle.
Assigning a Person Through FormFlow
FormFlow’s field library maps the People column to a multi-selection field the same way it maps Dropdown, Tags, and Name — “select from monday.com users,” listed with no separate note about a public-form restriction. That puts it on the same footing as every other supported column in the field library, unlike WorkForms’ account-data gate.
That said, FormFlow’s published docs don’t explicitly call out the public-vs-internal-form case the way monday.com’s own support article does for WorkForms. Before you put a People field on a form external respondents will fill out, confirm in your own account that:
- The field renders and lists the users you expect for a public (not account-restricted) form.
- The list of selectable people matches what you intend respondents to see — board members, workspace members, or the full account.
Treat this the way /blog/2026/fill-monday-columns-from-forms treats Connect Boards: state the documented capability, then verify the specific behavior on your own form rather than assuming it matches every edge case.
WorkForms vs FormFlow: People Column at a Glance
| WorkForms | FormFlow | |
|---|---|---|
| People on account-restricted forms | Supported | Supported |
| People on public forms | Requires an admin-enabled, account-wide toggle that exposes user data on every public form | Listed as a standard field; confirm exact public-form behavior in your own account |
| Assignment timing | At submission, once enabled | At submission |
| Alternative if you skip People | Auto-assign with an automation after the item is created | Auto-assign with an automation, same as WorkForms |
Setting Up Person Assignment
- In the FormFlow builder, add a People field from the field library and map it to your board’s People (or a custom people-type) column.
- Set whether the field is required, and whether respondents can pick more than one person if your column allows multiple assignees.
- Publish the form and submit a real test entry to confirm the assignee list matches who you expect to see.
- If you’d rather not expose a people-picker to external respondents at all, skip the field and use a monday.com automation to assign based on another field’s value instead — the same pattern the internal request system guide uses to route IT tickets by request type.
Frequently Asked Questions
Does every monday.com form need a People field to assign an owner?
No. Auto-assigning by automation after the item is created — for example, routing by request type or category — works without ever showing a people-picker to the respondent, and avoids the account-data exposure question on public forms entirely.
Can a public WorkForm show People without the admin toggle?
Not based on monday.com’s own documentation. The People question stays hidden on a public form until an admin enables the account-wide “Allow public account forms to use account data” setting, and enabling it applies to every public form on the account, not just one.
Does the People field on a public FormFlow form expose the same account data?
FormFlow’s documented field library doesn’t call out a separate public-form restriction for People, but confirm what the dropdown actually shows on your own public form before you rely on it, since the docs don’t detail the exact scoping.
What if I only want respondents to pick from a specific team, not the whole account?
Neither tool’s documentation describes filtering the People list to a subset of users on a public form. Scope the underlying board or workspace to the group you want listed, since both WorkForms and FormFlow read from board or workspace membership rather than the full account list when the board itself isn’t public.
Next Steps
- monday.com Column Types & Form Fields → — the full field library, including People
- Build an Internal Request System in monday.com → — auto-assign by request type instead of a people-picker
- 5 Ways to Automate Your Forms with monday.com Automations → — assignment automations after submission
- Time Off Request Form in monday.com → — People fields for employee and covering colleague
- Install FormFlow and map your first People field.
Last reviewed: 2026-09-26. WorkForms’ People column public-form restriction and the account-wide opt-in verified against monday.com’s People Column and WorkForms settings and permissions support articles. Features may change.