The upload users tool allows an administrator to perform multiple tasks at once, including but not limited to:
...
- For the System Administrator role, use "manager" (without the quotes)
- For the Supervisor role, use "supervisor"
- For the Course Creator role, use "coursecreator"
You can also unassign system roles by entering the same shortname of that role prefixed with a minus symbol: '-'. If the user is currently assigned to that role, they are removed from it. If the user is not currently assigned to that system role, the field value is ignored. However, the field value must refer to a system role that does exist on the system, otherwise an error will occur.
...
When the "New username duplicate handling" setting is set to "Append counter", an auto-increment counter will be appended to duplicate usernames produced by the template. For example, if the CSV file contains the users named John Doe, Jane Doe and Jenny Doe without explicit usernames, the default username is %-1f%-l and New username duplicate handling is set to Append counter, then the usernames produced will be jdoe, jdoe2 and jdoe3.
...
...
User Mapping & "Strict" Control
You can
...
specify a
...
"key" other than username when updating users. This is useful in the event that your HRIS does not track the user's username, which is typically only in Active Directory. You could for example use this feature to upload users by using their Employee ID as demonstrated in the screenshot below. The "key" must be unique across the system (for single-site systems ) and unique within a site (for /wiki/spaces/Healthcare/pages/34844303). If more than "key is found during the upload, the system will report an error.
If you do not have the username in the CSV file when uploading users, simply map the column from the CSV file to the database column in the learning environment using the "User mapping" option in the "Upload users" wizard.
...
If you enable the "Strict" option, the user mapping will ONLY be done on the Employee ID in the example below. In other words, if the Employee ID in the CSV file does not match an Employee ID in the database, then the system will skip the user. If the "Strict" option is disabled, the system will first attempt to match the users by Employee ID and if it doesn't find a match, it'll then make a second attempt and try to match the skipped users by mapping the username in the CSV to the username in the database.
(Note that the username is still required when creating users and as such, this feature is only available when updating users.)
Deleting Accounts
If the "deleted" field is present, users with value 1 for it will be deleted. In this case, all the fields may be omitted, except for username. After uploading the file, be sure to change the "Upload type" to "Update existing users only" and the "Allow deletes" option to "Yes".
...
The username is considered a key in the system for many functions such as uploading learning records and attendance records. As of version 3.5, you You can change the value of the username just like any other field, as long as "Allow renames" is set to "Yes'.
...