Make “Employee Number” Optional for Admins When Creating Staff-Type Users
Currently, when an admin creates a user through the admin interface and selects a staff-type user, the system enforces the "Employee Number" field as required—even if the field has been set to hidden or not required in the user registration settings.
This behavior seems inconsistent, especially since the visibility and requirement settings are generally expected to control whether the field must be filled in. While it makes sense for public-facing registration to enforce this, it would be more flexible and efficient for admin-side user creation to follow the same logic or allow overriding.
Proposed Change:
Allow the “Employee Number” requirement to be toggled or ignored during admin-side creation of staff-type users, based on the current visibility/requirement settings.
Why It Matters:
- Reduces unnecessary friction for administrators setting up test or temporary accounts.
- Makes admin-side behavior consistent with the configuration applied to the user-side registration.
- Supports more flexible use cases where an employee number is not always known or applicable at time of creation.
#12236