Important changes to Bulk user creation request procedure

In a change designed to assist establishments unable to use either USO-AutoUpdate or GroupCall to automate the management of staff and pupil USO user accounts, Atomwide has made changes to the bulk user request process. This is designed to improve data security, safe-guarding, and the accuracy of user data.

From today, newly-submitted bulk request spreadsheets must contain user details for the whole establishment (all staff entitled to a USO account, all students, or all entitled staff and students) with certain fields mandatory. It is anticipated that the fields in the spreadsheet will normally be populated with data derived from the establishment’s MIS, using its in-built export facilities.

Whole establishment spreadsheets uploaded via the support site will be put in the same automated queue for overnight processing that is used by the fully-automated MIS export systems. The results of the processing will then be made available on the User Accounts : Whole school bulk results page of the support site.

Wherever possible, USO-AutoUpdate software should be used instead of the manual process described above as AutoUpdate automatically exports user data from a establishment’s MIS, guaranteeing that USO account data is accurate and up-to-date.

Any questions about AutoUpdate or the all-school bulk update process should be raised via a support case. Full details regarding the installation of USO-AutoUpdate can be found in the Help section of the support site.

One thought on “Important changes to Bulk user creation request procedure

  1. Derek Biddle from HC - Governors EMS Site in Harrow;Derek Biddle from LA in Harrow;Derek Biddle from St Joseph's Catholic Primary School in Harrow says:

    Experience has shown that the key fields in the submission (names, date of birth and UPN) can change.

    Using the MIS unique Key field enables this to be overcome, and the process here (and the file example) cannot have this, and this could lead to have changing usernames when changes happen.

    However, once a file has been processed, there WILL be a unique field value – it would be called the USO username, and if a file was sent back or downloaded for adjustment, this might be avoided.

    Derek Biddle

Leave a Reply