On admin/accounts/new (src/main/resources/templates/accounts/new.html), when the selected Role is Admin or Mentor, the "Intern details" inputs (Student code, Internship start, Internship end) remain editable, inviting misinput. They should be visually grayed out and non-interactive unless the Role is Intern. This is a UI-only guard; keep existing server-side validation.
On admin/accounts/new (src/main/resources/templates/accounts/new.html), when the selected Role is Admin or Mentor, the "Intern details" inputs (Student code, Internship start, Internship end) remain editable, inviting misinput. They should be visually grayed out and non-interactive unless the Role is Intern. This is a UI-only guard; keep existing server-side validation.
dochim
changed title from Admin: disable Intern to Admin: disable "Intern details" fields when role is not Intern2026-08-15 21:22:57 +07:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On admin/accounts/new (src/main/resources/templates/accounts/new.html), when the selected Role is Admin or Mentor, the "Intern details" inputs (Student code, Internship start, Internship end) remain editable, inviting misinput. They should be visually grayed out and non-interactive unless the Role is Intern. This is a UI-only guard; keep existing server-side validation.
Admin: disable Internto Admin: disable "Intern details" fields when role is not Intern