Driver’s Role
This screen is a role-specific extension of the general user creation form. When the user selects “Driver” as the role, additional fields relevant to driver-specific user profiles become visible. This ensures accurate data entry and improves application personalization.
Form Fields
Role*
- Selected Value:
Driver - Function: Determines dynamic field visibility (e.g., shows driver-specific fields).
- Placeholder:
email@email.com - Validation: Optional (no asterisk).
Phone Number*
- Placeholder:
+ 12345678900 - Validation: Required
First Name*
- Placeholder:
John - Validation: Required
Last Name*
- Placeholder:
Doe - Validation: Required
Driver-Specific Fields
Driver’s App Language*
- Type: Dropdown select
- Purpose: Defines the language for the driver’s mobile or web application UI.
- Validation: Required
- Expected Options: Could include “English”, “Poland”, “Russian”.
Driver is an Employee*
- Type: Toggle switch (default: off)
- Purpose: Indicates whether the driver is employed directly or externally contracted.
- Validation: Required (based on asterisk)
- States:
- Off: Driver is not an employee.
- On: Driver is an employee.
Action Buttons
Save
- Label:
Save - Icon: Disk/save icon
- Function: Triggers form validation and user creation process.
- Availability: Likely disabled until all required fields are correctly populated.
Dynamic Behavior Summary
| Trigger | Effect |
|---|---|
Selecting Driver as Role | Reveals additional fields: App Language & Employment Status |
| Toggling “Driver is an employee” | Marks internal employment, may impact permissions or payroll workflows |
| Incomplete required fields | Prevents form submission |
Validation & UX
- Required fields marked with
*. - Placeholder text assists data entry.
- Consistent styling promotes form comprehension.
- Logical grouping improves cognitive flow (User Identity → Contact Info → Driver Settings).
