Upload users in Moodle Workplace
The Upload users tool is enhanced in Moodle Workplace to allow additional functionality.
A tenant can be specified using tenant field when uploading the CSV by users with the capability tool/tenant:allocate. These users will be able to specify a tenant when uploading users (both when creating new users and updating existing).
If the current user does not have this capability, they can only create/update users in their own tenant. Use of tenant field is not allowed to these users. Note that by default, only site admins have this capability.
Example of the CSV file:
username,firstname,lastname,email,tenant jonest,Tom,Jones,email@example.com,big reznor,Trent,Reznor,firstname.lastname@example.org,small
Tenants are matched by their "ID number".
If the current user has the capability to assign jobs (in addition to the capability to use the upload user tool), they can create jobs for users or modify dates for existing jobs. Both fields jobdepartment1 and jobposition1 must have values, and fields jobstartdate1 and jobenddate1 are optional. When a user already has a job in this department and position, the dates will be modified but the new job will not be created, in this case, empty values in start/end date fields will mean "do not modify", to remove the job end date it can be set to "0". Departments and positions are matched by their "ID number" just like tenants. It is possible to add more than one job for one user in the same line by adding jobdepartment2, jobposition2, etc.
username,firstname,lastname,email,jobdepartment1,jobposition1,jobstartdate1,jobenddate1 jonest,Tom,Jones,email@example.com,exampledep,examplepos,, reznor,Trent,Reznor,firstname.lastname@example.org,exampledep2,examplepos2,2019-05-07, jon,Jon,Whatever,email@example.com,exampledep2,examplepos2,2019-05-07,2032-01-09
To delete a job assignment, make use of the jobdelete1 field, as shown in the following example.
username,jobdepartment1,jobposition1,jobdelete1 user1,dep1,pos1,1 user2,dep1,pos1,0
When the value is set to 1, the record will be deleted; if it is set to 0 the record will be kept.
Programs and certifications allocations
If the current user has the capability to allocate to programs and/or certifications (in addition to the capability to use the upload user tool), they can do so in the upload users tool. Only users, programs and certifications from the same tenant can be used. If the user already has a direct (manual) allocation to a program/certification or via dynamic rules, the dates will be updated. Programs and certifications are matched by their "ID number".
username,program1,programstartdate1,programenddate1,programduedate1 user14,prog1,2019-05-12,, user15,prog1,2019-05-12,2032-01-09,2032-01-09 user12,prog1,2019-05-12,2032-01-09, user13,prog1,2019-05-12,,2032-01-09
Example 1 - allocating users to certification and/or updating dates in the existing allocation (start and due date can not be updated for users who are already certified or have started recertifications):
username,certification1,certificationstartdate1,certificationduedate1 user14,cert1,2019-05-12, user15,cert1,2019-05-12,2032-01-09
Example 2 - marking users as certified:
Example 3 - updating the expiry date for the users who are already certified:
If the current user has the 'tool/datastore:uploadcoursecompletion' capability, they can upload course completion data to be stored in the Data store for users who belong to the same tenant as themselves. This data can be reported on by using the Report builder report source "Course completion from datastore".
Details on the course completion mechanism can be found in a dedicated section in the Report builder docs.