# Assignee The Assignee field is a first-class field type that links records to users in your app. It works like a relationship to the [Users table](/users-and-permissions/user-table.md) without requiring you to manually set up the relationship, and it comes with built-in assignment notifications. ## How It Works * The Assignee field creates a direct link between a record and one or more users * You can configure the field to allow a **single assignee** or **multiple assignees** * When a user is assigned to a record, they can optionally receive a notification * Assigned users are automatically included in [record comment](/record-pages/record-comments.md) notifications while they remain assigned ## Adding an Assignee Field 1. Open the table you want to add the field to 2. Click 'New Field' 3. Add a new field and choose **Assignee** as the type 4. Choose whether to allow single or multiple assignees 5. Configure notification preferences ## Configuration Options * **Single Assignee** Only one user can be assigned to a record at a time. Assigning a new user replaces the previous one. * **Multiple Assignees** Multiple users can be assigned to a single record simultaneously, useful for shared ownership or team-based work. * **Assignment Notifications** Optionally notify users when they are assigned to a record, so they know work is waiting for them. ## Notification Behavior The Assignee field integrates with Noloco's [notification system](/notifications/notifications.md): * **On assignment**: Users can receive a notification when they are assigned to a record * **Comment notifications**: While assigned, users are automatically subscribed to [record comments](/record-pages/record-comments.md) and notes on that record * **On unassignment**: When a user is unassigned, they are unsubscribed from that record's comment notifications — unless they are subscribed through other means (e.g. they commented on or were mentioned in the record) ## Use Cases Assignee fields are ideal for: * Task and ticket management — assign work items to team members * Approval workflows — assign a reviewer or approver to a record * Case management — assign a case owner to customer requests * Project management — assign team members to deliverables * Support queues — route issues to specific agents ## Integration with Other Features * [**Record-level permissions**](/users-and-permissions/user-roles-and-permissions/record-level-permissions.md): Use the Assignee field to restrict access so users only see records assigned to them * [**Filters**](/views/filters/logged-in-user.md): Filter views by the logged-in user to build "My Tasks" or "Assigned to Me" views * [**Workflows**](/workflows/workflows.md): Trigger workflows when a record is assigned or reassigned * [**Notifications**](/notifications/notifications.md): Keep assignees informed about activity on their records ## Assignee vs. a Manual User Relationship You could achieve similar linking by creating a standard [relationship](/data/collections/relationships.md) to the Users table, but the Assignee field offers several advantages: * **No manual wiring** — the link to the Users table is set up automatically * **Built-in notifications** — assignment and comment notifications work out of the box * **Automatic subscriptions** — assignees stay informed without extra configuration * **Semantic clarity** — the field communicates its purpose clearly in your data model ## Best Practices * Use a single assignee when records need a clear owner (e.g. a primary contact or responsible person) * Use multiple assignees for collaborative work where several people share responsibility * Enable assignment notifications so users know when they have new work * Combine with [logged-in user filters](/views/filters/logged-in-user.md) to build personal dashboards * Pair with status or priority fields to help assignees triage their work ## FAQs 1. **What's the difference between an Assignee field and a relationship to the Users table?** An Assignee field is a purpose-built relationship to the Users table that requires no manual wiring and comes with built-in assignment notifications and automatic comment subscriptions. A standard [relationship](/data/collections/relationships.md) gives you the same data link but without these extras. 2. **Can I have multiple Assignee fields on the same table?** Yes. For example, you could have one Assignee field for "Owner" and another for "Reviewer" if your workflow requires different assignment roles. 3. **What notifications do assignees receive?** Depending on your configuration, assignees can receive a notification when they are assigned. While assigned, they are also automatically subscribed to [record comment](/record-pages/record-comments.md) notifications on that record. 4. **What happens when a user is unassigned?** They are unsubscribed from that record's comment notifications — unless they are subscribed through other means, such as having commented on or been mentioned in the record. 5. **Can I turn off assignment notifications?** Yes. Assignment notifications are optional and can be configured when setting up the Assignee field. 6. **Does the Assignee field work with permissions?** Yes. You can use the Assignee field in [record-level permissions](/users-and-permissions/user-roles-and-permissions/record-level-permissions.md) to restrict access so users only see or edit records assigned to them. 7. **Can I assign users who haven't been invited to the app yet?** No. Only users who exist in your [Users table](/users-and-permissions/user-table.md) can be assigned. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guides.noloco.io/data/collections/field-types/assignee.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.