Overview
DemandFlow provides two field types for selecting users from your organisation:
- Single User (
singleuser) — select one user - Multi User (
multiuser) — select multiple users
Both field types display user names with avatar previews and provide a searchable picker for finding the right person. They are essential for assigning ownership, responsibility, and accountability on records.
Single User Properties
| Property | Required | Description |
|---|---|---|
| ID | Yes | The field identifier. |
| Type | Yes | Must be set to singleuser |
| Name | Yes | The display label. |
| Width | No | The percentage width. |
| Required | No | When true, a user must be selected. |
| Read Only | No | When true, the assigned user is displayed but cannot be changed. |
| Grid | No | When true, appears as a column in list views with the user's name. |
| Help | No | Tooltip text. |
| Visibility | No | A condition controlling visibility. |
Multi User Properties
The Multi User field supports the same properties as Single User but allows selecting multiple people. Selected users are displayed as a list, with each user's name and avatar shown.
User Picker
When a user clicks on a user selection field, a search picker opens. The picker allows users to:
- Search for users by name
- Browse available users
- See user avatars for easy visual identification
- Select one or multiple users depending on the field type
Use Cases
| Field Type | Example Uses |
|---|---|
| Single User | Record owner, task assignee, project manager, approver, reviewer |
| Multi User | Team members, stakeholders, watchers, review board, attendees |
Best Practices
- Use Single User for clear single-person accountability (owner, assignee, approver)
- Use Multi User for groups (team members, stakeholders, reviewers)
- Enable Grid on assignee/owner fields so records can be filtered by person in list views
- Set Required on owner or assignee fields to ensure every record has a responsible person
- A width of 50% works well for user fields