Jamf School currently assigns users and devices based on the following premises:

• Each user is assigned a username, which Jamf School treats as a unique identifier.
• Devices are linked to users via this username.

However, there is a design flaw in the current implementation:

• It is possible to create new users with an already existing username, either manually or via CSV import.
• Jamf School does not issue a warning or automatically adjust the username (e.g., by appending a number).
• The original user is silently deleted, and a new user with the same username is created.
• All devices previously assigned to the original user are now assigned to the new user.
• This behavior occurs across the entire Jamf School instance, including across different locations.

Jamf School should enforce globally unique usernames across all locations.
Since location managers can only view users within their own location, they cannot verify whether a username already exists elsewhere.

Therefore, Jamf should implement a centralized validation mechanism or enforce a naming convention for usernames across all locations to prevent such conflicts.