Users - Revision history

Mannysingh at 14:47, 29 September 2021

2021-09-29T14:47:27Z

Admin: /* User permissions */

2017-11-21T16:06:42Z

User permissions

Admin: /* User permissions */

2017-11-21T16:04:56Z

User permissions

Admin: /* User permissions */

2017-11-21T15:55:50Z

User permissions

Admin: /* User permissions */

2016-08-30T10:15:04Z

User permissions

Admin: /* User permissions */

2016-08-30T09:42:56Z

User permissions

Admin: /* Affinities */

2016-08-26T15:19:01Z

Affinities

Admin: /* User permissions */

2016-08-26T14:44:10Z

User permissions

Admin: /* Reset Secret */

2016-08-22T15:50:21Z

Reset Secret

Admin: /* Reset Secret */

2016-08-22T15:49:17Z

Reset Secret

@@ Line 21: / Line 21: @@
 <div style="color:#ffffff"> <br> '''Account manager'''
 :This allows a user to modify other users' permissions. The initial admin account will always have this permission, and no other user can be given this permission. This also allows the user to access the '''[[system settings|<span style="color:#ff8800">system settings</span>]]'''.
 '''Data entry'''
 :This must be active for users to record Concerns, Meetings, Correspondances or Actions. See '''[[Recording information|<span style="color:#ff8800">recording information</span>]]''' for more info.

@@ Line 28: / Line 28: @@
 :This allows the user to apply custom created tags created in 'Configuration' tab to be applied to the student.
 '''Data controller'''
-:This provides the permission for individual to have access to the 'Data Protection' configuration page for your school.
+:This provides the permission for individual to have access to the '''[[Data Protection|<span style="color:#ff8800">Data Protection</span>]]''' configuration page for your school.
 '''Data configuration'''
 :This allows the user to amend subcategories under Meetings, Correspondances or Actions for '''[[data configuration|<span style="color:#ff8800">data configuration</span>]]'''. The user can also specify certain websites that are to be used under the Links area, visible under the '''[[resources|<span style="color:#ff8800">resources</span>]]''' screen.

@@ Line 24: / Line 24: @@
 :This must be active for users to record Concerns, Meetings, Correspondances or Actions. See '''[[Recording information|<span style="color:#ff8800">recording information</span>]]''' for more info.
 '''Levels of need manager'''
+:This allows the user to enter information provided to them from Local Safeguarding Boards onto the student 'Personal details' screen.
 '''Personal tag manager'''
+:This allows the user to apply custom created tags created in 'Configuration' tab to be applied to the student.
 '''Data controller'''
+:This provides the permission for individual to have access to the 'Data Protection' configuration page for your school.
 '''Data configuration'''
 :This allows the user to amend subcategories under Meetings, Correspondances or Actions for '''[[data configuration|<span style="color:#ff8800">data configuration</span>]]'''. The user can also specify certain websites that are to be used under the Links area, visible under the '''[[resources|<span style="color:#ff8800">resources</span>]]''' screen.
@@ Line 57: / Line 57: @@
 '''Tag based limits'''
+:This area allow the administrator to configure tags that hide information from screens.
 ==Affinities==

@@ Line 23: / Line 23: @@
 '''Data entry'''
 :This must be active for users to record Concerns, Meetings, Correspondances or Actions. See '''[[Recording information|<span style="color:#ff8800">recording information</span>]]''' for more info.
 '''Data configuration'''
 :This allows the user to amend subcategories under Meetings, Correspondances or Actions for '''[[data configuration|<span style="color:#ff8800">data configuration</span>]]'''. The user can also specify certain websites that are to be used under the Links area, visible under the '''[[resources|<span style="color:#ff8800">resources</span>]]''' screen.
@@ Line 49: / Line 55: @@
 '''Require two factor login'''
 :If this option is selected then the user will need to use an authenticator on their phone, tablet or mobile device in order to login. This gives a greater level of security. See the '''[[Logging in#Pin number access for added security|<span style=";">logging in</span>]]''' page for more information about PIN numbers. <br> <br>
 ==Affinities==

@@ Line 45: / Line 45: @@
 '''Simplified interface'''
-:The simplified interface is used for users who will never need to review any incidents. They can only record information and not review anything that has happened. Users who are using the simplified interface will not see the '''[[home page|<span style="">home page</span>]]'''. If they have the Data Entry permission, then their login will default to the '''[[students|<span style="">students</span>]]''' page. Users who have been given a review severities range cannot also use the simplified interface. <br> <br>
+:The simplified interface is used for users who will never need to review any incidents. The users can only record information and not review anything that has happened. Users who are using the simplified interface will not see the '''[[home page|<span style="">home page</span>]]'''. If they have the Data Entry permission, then their login will default to the '''[[students|<span style="">students</span>]]''' page. Users who have been given a review severities range cannot also use the simplified interface. <br> <br>
 '''Require two factor login'''

@@ Line 39: / Line 39: @@
 '''Severity'''
-:Each recorded piece of information in Cura must be given a severity level between 1 and 5. The higher the severity, the more concerning the information is. See the '''[[students|<span style="">students</span>]]''' page for more information about recording information in Cura. <br> <br>
+:Each recorded piece of information in Cura must be given a severity level between 1 and 5. The higher the severity, the more concerning the information is. See the '''[[students|<span style="">students</span>]]''' page for more information about recording information in Cura. <br>
 :A user's severity range dictates which pieces of information they will be responsible for acting upon. Users will either need to act on every incident within their severity range (e.g. the Child Protection Officer may want to deal with all Severity 5 incidents), or only the incidents within their severity range that affect students they share an affinity with (e.g. a form tutor may only deal with incidents affecting students in his/her form). <br> <br>

@@ Line 52: / Line 52: @@
 ==Affinities==
-Next to the review severities is a '''"Limit to affinities"''' box. This allows you to link a user to specific pupils, so that the user will be alerted whenever information is recorded about that child (as long as the user's clearance level is high enough to view the information). <br> <br>
+Next to the review severities is a '''"Limit to affinities"''' box. This allows you to link a user to specific pupils, so that the user will be alerted whenever information is recorded about that child ('''as long as the user's clearance level is high enough to view the information'''). <br> <br>
 For more information about how to configure this, please see the '''[[affinities|<span style="">Affinities</span>]]''' page. <br> <br>

@@ Line 12: / Line 12: @@
 '''Clearance'''
-:The user's clearance level decides which pieces of information they are able to view. When a staff member records something in Cura, they will need to give a clearance level between 1 and 5. The higher the clearance, the more sensitive the information is. A staff member can record an incident using any clearance level however they will not be able to review incidents above their clearance level. See the '''[[Recording information|<span style="">Recording information</span>]]''' page for more information about recording information in Cura. <br> <br>
+:The user's clearance level decides which pieces of information they are able to view. When a staff member records something in Cura, they will need to give a clearance level between 1 and 5. The higher the clearance, the more sensitive the information is. A staff member can record an incident using any clearance level, however they will not be able to review incidents above their clearance level. See the '''[[Recording information|<span style="">Recording information</span>]]''' page for more information about recording information in Cura. <br> <br>
 :This will have the most noticeable effect on the '''[[home page|<span style="">home page</span>]]''', which is used for reviewing incidents. <br> <br>

@@ Line 60: / Line 60: @@
 The reset secret button allows you to generate a new secret code which is needed to generate PIN numbers. PIN numbers are only required by users who have the '''"Require two factor login"''' permission switched on. These users will need a PIN number which will be generated by an authenticator app on their phone, tablet or mobile device. <br> <br>
-If a user requires two factor login, then they will be given a secret code the first time they try to login. If the user does not record their secret code, or they lose the device that the secret code was saved onto, then the '''Reset Secret''' button should be used. This will invalidate the old code, and offer the user a new one the next time they try to log in. Simply select the user(s) and click on the '''Reset Secret''', a message box will appear '''"Are you sure you want to reset this user's secret?"''', click on the '''"Ok"''' button to confirm. A message box will appear confirming the secret has been reset '''"Reset complete"'''.<br> <br>
+If a user requires two factor login, then they will be given a secret code the first time they try to login. If the user does not record their secret code, or they lose the device that the secret code was saved onto, then the '''Reset Secret''' button should be used. This will invalidate the old code, and offer the user a new one the next time they try to log in.
 [[Image:users04.jpg|800px]] <br> <br>