> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/screens-and-components/type-of-components/user-field.md).

# User field component

Show or select people in relation to your **Users** database / people-like properties inside screens and forms.

## When to use

* Assignee / owner pickers tied to App Users
* Displaying who a record belongs to on Details
* Directory-style fields that should resolve to Users rows

## Maker setup

1. Prefer a Notion **relation** to the Users database when personalization matters.
2. Add the **User field** component and bind the property.
3. Combine with [Data Restriction](https://docs.notionapps.com/users/data-restriction) so users only see appropriate rows elsewhere.
4. For list filtering by logged-in user properties, see [Filter lists…](https://docs.notionapps.com/how-to-guides/filter-list-screens-by-logged-in-user-properties) (entitlement-gated).

## Tips

* Guest Notion users may not appear in some dropdowns — see Troubleshooting FAQ on guest users in dropdowns.
* Keep the Users database email property clean; User field UX depends on healthy App Users data.
* After Users schema changes, reload databases and re-test View as + a real login.

## Related

* [App Users](https://docs.notionapps.com/users/app-users)
* [People / status fidelity](https://docs.notionapps.com/how-to-guides/status-and-people-field-fidelity)
* [Employee Directory](https://docs.notionapps.com/use-cases/employee-directory)