User management - Revision history

Jrobertson at 23:45, 13 February 2018

2018-02-13T23:45:29Z

2018-01-09T02:53:32Z

Bulk User add

2017-11-23T02:01:35Z

2017-11-22T03:00:15Z

Bulk User add

2017-11-22T00:47:44Z

2017-11-21T22:16:00Z

Additional Attributes

2017-11-21T22:15:45Z

Additional Attributes

2017-11-21T22:15:23Z

Additional Attributes

2017-11-21T22:14:42Z

Bulk User add

2017-11-21T22:14:09Z

Bulk User add

← Older revision		Revision as of 23:45, 13 February 2018
Line 130:		Line 130:

	This will tell the upload facility that the password is already encrypted and it does not need to do any further encryption.		This will tell the upload facility that the password is already encrypted and it does not need to do any further encryption.
−
−	~~[[Category:Cloudwork Dashboard]]~~

@@ Line 71: / Line 71: @@
 Your CSV file should contain the following headings:
-Email, User Name, First Name, Last Name, Password, Role
+Email, User Name, First Name, Last Name, Password, Role, SIS_ID
-e.g. Email, User Name, First Name, Last Name, Password, Role
+e.g. Email, User Name, First Name, Last Name, Password, Role, SIS_ID
-  principal@example.edu.au,principal,School,Principal,pri2009,teacher
+  principal@example.edu.au,principal,School,Principal,pri2009,teacher, 23
-  joeblogs@example.edu.au,joeblogs,joe,blogs,joe2009,teacher
+  joeblogs@example.edu.au,joeblogs,joe,blogs,joe2009,teacher, 24
-  a.student@example.edu.au,SN1234,Alfred,Student,as2010,student
+  a.student@example.edu.au,SN1234,Alfred,Student,as2010,student, 25
 The following email accounts will be created:
@@ Line 85: / Line 85: @@
   a.student@example.edu.au with a password of as2010, and a SSO username of SN12345678
 Valid roles must be chosen from the following list:

← Older revision		Revision as of 02:01, 23 November 2017
Line 129:		Line 129:
	This will tell the upload facility that the password is already encrypted and it does not need to do any further encryption.		This will tell the upload facility that the password is already encrypted and it does not need to do any further encryption.

−	[[Category:Dashboard]]	+	[[Category:Cloudwork Dashboard]]

@@ Line 109: / Line 109: @@
 With the extra attributes the CSV file may looks like this:
-  Email, User Name, First Name, Last Name, Password, Role, Recovery Email, Recovery Phone
+  Email, User Name, First Name, Last Name, Password, Role, Recovery Email, Recovery Phone, SynID
-  principal@example.edu.au,principal,School,Principal,pri2009,teacher, othermail@gmail.com, 0412345678
+  principal@example.edu.au,principal,School,Principal,pri2009,teacher, othermail@gmail.com, 0412345678, 314159
-  joeblogs@example.edu.au,joeblogs,joe,blogs,joe2009,teacher, joemail@gmail.com, 045678910
+  joeblogs@example.edu.au,joeblogs,joe,blogs,joe2009,teacher, joemail@gmail.com, 045678910, 123456
-  a.student@example.edu.au,SN1234,Alfred,Student,as2010,student, sparemail@gmail.com, 042345678
+  a.student@example.edu.au,SN1234,Alfred,Student,as2010,student, sparemail@gmail.com, 042345678, 234566
 As well as another attribute called SynID. Once the user logs in, all the normal attributes will be created and sent to the service provider, additionally this user will have SynID sent. ''NB Password reset information is NOT exposed to service providers.''

← Older revision		Revision as of 00:47, 22 November 2017
Line 128:		Line 128:

	This will tell the upload facility that the password is already encrypted and it does not need to do any further encryption.		This will tell the upload facility that the password is already encrypted and it does not need to do any further encryption.
		+
		+	[[Category:Dashboard]]

@@ Line 115: / Line 115: @@
 As well as another attribute called SynID. Once the user logs in, all the normal attributes will be created and sent to the service provider, additionally this user will have SynID sent. ''NB Password reset information is NOT exposed to service providers.''
 So when the user is created all the information about the user is already there without need for further interaction.
 Just to make things clear on these new attributes, they can be left blank for users that they do not apply, or just simply not included in the import.

← Older revision		Revision as of 22:14, 21 November 2017
Line 105:		Line 105:

	These are not compulsory and can be left blank for the users that do not have such a value.		These are not compulsory and can be left blank for the users that do not have such a value.
		+
		+
		+	With the extra attributes the CSV file may looks like this:
		+
		+	Email, User Name, First Name, Last Name, Password, Role, Recovery Email, Recovery Phone
		+	principal@example.edu.au,principal,School,Principal,pri2009,teacher, othermail@gmail.com, 0412345678
		+	joeblogs@example.edu.au,joeblogs,joe,blogs,joe2009,teacher, joemail@gmail.com, 045678910
		+	a.student@example.edu.au,SN1234,Alfred,Student,as2010,student, sparemail@gmail.com, 042345678
		+
		+	As well as another attribute called SynID. Once the user logs in, all the normal attributes will be created and sent to the service provider, additionally this user will have SynID sent. NB Password reset information is NOT exposed to service providers.
		+
		+	So when the user is created all the information about the user is already there without need for further interaction.

	=== Bulk user add - Encrypted passwords ===		=== Bulk user add - Encrypted passwords ===