User Select
User Select selects one or more users from the platform directory. It participates in the state, validation, and submission boundary of its Form.
1. When to use it
Typical uses:
- Requester, owner, or approver
- Collaborators
- People fields submitted by user ID
2. Add and configure
- Add User Select to the Fields slot of a Form Section.
- Set a stable, unique Field Key / Name that matches the backend DTO property.
- Configure the component properties below, then add Required, Help Text, Full row, or conditions as needed.
- Check the initial value and layout in Design Preview, then use Form Validate / Submit to test the full data path.
3. Main properties
| Property | Purpose |
|---|---|
| Display Name | Controls how the field is displayed in Design Preview and Runtime. |
| Multiple | Enables or disables this behavior. |
| Required | Enables or disables this behavior. |
| Help Text | Controls how the field is displayed in Design Preview and Runtime. |
| Disabled When | Defines the data shape used for binding, submission, or responses. |
Common properties such as Field Key, Required, Help Text, Full row, and Visible When come from the Form field contract. The table highlights the settings most relevant to User Select.
4. Form value and backend contract
Submitted value: A stable option value in single mode, or an array of option values in multiple mode.
"user-8f13"
["user-8f13", "user-a204"]
The example shows the data shape only. The API must still validate type, range, and authorization against its business DTO.
5. Validation, conditions, and interactions
Every field can use Form properties such as Required, Visible When, Disabled When, Required When, Dependencies, and Clear When Hidden. Conditions improve interaction but never replace backend validation or authorization.
Component capabilities: The value participates in Form state; only events exposed in the property panel are available to Interaction.
6. Recommendations
Recommendations: Submit stable user or department IDs; display names are for presentation only. The backend must recheck tenant scope and authorization.
Return to the Form overview for layout, validation, submission, drafts, and backend protocol guidance.