> ## Documentation Index > Fetch the complete documentation index at: https://zite.com/llms.txt > Use this file to discover all available pages before exploring further. # Link records to people with a user field > Attach records to the people who use your app or workspace, so you can show each person their own data. ## How it works A user field links a record to one or more people in the workspace. That person can be an editor, an internal app member, or an external user. Use the field for owners, assignees, submitters, and similar relationships. Every app in the workspace uses the same user directory, so the field links directly to one shared record for each person. ### Common use cases * Assign tasks to teammates and give each person their own queue * Show customers their orders, invoices, or documents in a client portal * Store a phone number, department, or plan for each person who signs in * Record who reviewed or submitted a request * Build a team page that shows who is responsible for what ## Add a user field Click `+ Add field` and choose `User`. Name the field after what the person *is* in that table: `Owner`, `Assignee`, `Reviewer`, `Submitted by`, or `Member`. Choose whether the field holds one person or several, who appears in the picker, and what happens to the row when that person leaves. Each setting is covered below. ## Field settings | Setting | What it does | | - | - | | **Allow multiple users** | Let this field hold more than one user per row. Turning it off permanently removes all but the first user from rows that already have several. | | **Internal users only** | Only show editors and internal app members in the picker. External users are hidden. | | **Delete row when user is deleted** | Delete the row when that person is deleted from the workspace. Only available when the field holds a single user. | Turning **Allow multiple users** off is destructive. Rows that hold several people keep only the first, and the rest can't be recovered. **Internal users only** filters the picker in the database. It doesn't stop an app, workflow, or the API from setting the field to someone else. ## Delete row when user is deleted Turn this on when the row represents the person, such as a profile, membership, or per-user settings record. If the person is deleted from the workspace, their row is deleted too. Leave it off for rows that belong to the work rather than the person. Deleting an `Assignee` shouldn't delete the task, and deleting a `Submitted by` shouldn't delete the request. * The setting applies across the workspace, not per app. Removing access to one app leaves the person's rows alone. * Deletion is permanent. Re-adding the person later does not restore their rows. * The field must allow one user. The setting is hidden when **Allow multiple users** is on because the row could belong to several people. ## Last modified by `Last modified by` records who most recently changed a record. Zite fills it automatically. You cannot set it yourself, and it is not included when you import data. Use it for audit trails or "who changed this last" columns. Use a user field when you need to assign someone. ## See your users The database shows the workspace's user directory in a read-only panel. To store more details about someone, add the fields to one of your tables and link that table with a user field. Manage access from `Users`, to the left of the workspace selector. Choose `Editors` or an individual app from the side menu. See [Members & users](/help/platform/access/manage-users).