Difference between revisions of "Profile Updates"

From UnionCloud Support
Jump to: navigation, search
 
Line 1: Line 1:
 
{{PAGENAME}} is a stub, and just part of a wider section on UnionCloud Setup, for the full UnionCloud setup index please check the page [[Setup|here]].<br/><br/>
 
{{PAGENAME}} is a stub, and just part of a wider section on UnionCloud Setup, for the full UnionCloud setup index please check the page [[Setup|here]].<br/><br/>
 
[[File:Profile Updates.PNG|thumb|Profile Updates screen]]
 
[[File:Profile Updates.PNG|thumb|Profile Updates screen]]
'''Profile Updates''' is one of the simpler sections from Setup. It simply consists of 5 dropdown boxes, allowing you the Administrator to set whether users have the ability to update certain profile information or not, the fields you can set are;
+
'''Profile Updates''' is one of the simpler sections from Setup. It simply consists of various dropdown boxes, allowing you the Administrator to set whether users have the ability to update certain profile information or not, the fields you can set are;
 
*Forename
 
*Forename
 
*Surname
 
*Surname
 +
*Email
 
*Date of Birth
 
*Date of Birth
 +
*Gender
 
*Nationality
 
*Nationality
*Month/Year in which course finishes.
+
*Placement
 +
*Institution email
 +
*Domicile country
 +
*University id
 +
*Alternate email address
 +
*Ethnicity
 +
*Finalist
 +
*Mode of study
 +
*Address & Postcode
 +
*Library card
 +
*Fee status
 +
*Department
 +
*Erasmus
  
 
The two options you have for these fields are as follows;
 
The two options you have for these fields are as follows;
Line 12: Line 26:
 
*Student Can Not Update
 
*Student Can Not Update
  
As of August 2017 if you allow a student to update these fields, if the university provide an update which doesn't match, the information the student has set manually will override what the university sends.<br/>
+
However, it is highly recommended that you keep all fields to '''Student Can Update''' to align with GDPR regulations, if you switch off a student’s ability to update information about themselves you should provide another mechanism for them to update their data.
The reasoning for this is for example if people have preferred names, or for example in the case of a Trans student, if they have changed name, but haven't yet informed the university, then the university could change their name back in UnionCloud via data transfer to their '[http://gender.wikia.com/wiki/Deadnaming Dead Name]'.<br/>
+
 
As such some of these fields you may want to carefully lockdown for example, although you may want to allow them to change their name, you may not want them to change their Course End date, something which in most cases should only be set by the institution.
+
As of August 2017 if you allow a student to update these fields, if the university provide an update which doesn't match, the information the student has set manually will override what the university sends. The reasoning for this is for example if people have preferred names, or for example in the case of a Trans student, if they have changed name, but haven't yet informed the university, then the university could change their name back in UnionCloud via data transfer to their '[http://gender.wikia.com/wiki/Deadnaming Dead Name]'.

Latest revision as of 09:46, 26 July 2018

Profile Updates is a stub, and just part of a wider section on UnionCloud Setup, for the full UnionCloud setup index please check the page here.

Profile Updates screen

Profile Updates is one of the simpler sections from Setup. It simply consists of various dropdown boxes, allowing you the Administrator to set whether users have the ability to update certain profile information or not, the fields you can set are;

  • Forename
  • Surname
  • Email
  • Date of Birth
  • Gender
  • Nationality
  • Placement
  • Institution email
  • Domicile country
  • University id
  • Alternate email address
  • Ethnicity
  • Finalist
  • Mode of study
  • Address & Postcode
  • Library card
  • Fee status
  • Department
  • Erasmus

The two options you have for these fields are as follows;

  • Student Can Update
  • Student Can Not Update

However, it is highly recommended that you keep all fields to Student Can Update to align with GDPR regulations, if you switch off a student’s ability to update information about themselves you should provide another mechanism for them to update their data.

As of August 2017 if you allow a student to update these fields, if the university provide an update which doesn't match, the information the student has set manually will override what the university sends. The reasoning for this is for example if people have preferred names, or for example in the case of a Trans student, if they have changed name, but haven't yet informed the university, then the university could change their name back in UnionCloud via data transfer to their 'Dead Name'.