Difference between revisions of "Users"
|Line 48:||Line 48:|
'''Require two factor login'''
'''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
: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]] page for more information about PIN numbers. <br> <br>
Revision as of 15:15, 22 August 2016
If any staff members have been imported into the system, you will see a list of them on this page, as well as the initial admin user. If you have not imported any users into the system, see our import page for instructions to do so.
One or more staff members can be selected using the checkboxes. Once you have selected the staff member(s), click the "Open" button at the top right of the page. You will see a window where you can alter user(s) permissions.
- By default, users are approved. This means that Cura will recognise them and allow them to perform actions in the system (as long as they have any other required permissions, see below). If a user is not approved, they will not be able to log in, regardless of their other permissions.
- 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 page for more information about recording information in Cura.
- This will have the most noticeable effect on the home page, which is used for reviewing incidents.
- 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 page for more information about recording information in Cura.
- 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).
- If a user's severity range is not above 0, they will not have to act upon any incidents. Incidents that need to be actioned are dealt with via the home page.
- 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. If they have the Data Entry permission, then their login will default to the students page. Users who have been given a review severities range cannot also use the simplified interface.
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 page for more information about PIN numbers.
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).
For more information about how to configure this, please see the Affinities page.
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.
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.