Users

From CuraWiki
Jump to: navigation, search

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.

Users01.jpg

User permissions

Approved

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.

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 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.

Curaperms2.jpg


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.

Data entry

This must be active for users to record Concerns, Meetings, Correspondances or Actions. See recording information 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. The user can also specify certain websites that are to be used under the Links area, visible under the resources screen.

Data importer

This gives access to the import page, used to import children and staff into Cura.

Archivist

This gives the user access to archive students or transfer the existing data to another school.

Resource manager

Upload resources, such as contact forms and policies, for other users to download.

Resource consumer

This allows users to download resources that have been imported into Cura (see above), and also use the websites configured in the data configuration screen.

Report runner

A Report Runner is allowed to run reports to analyse the data that has been recorded in Cura.

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 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.

Simplified interface

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. 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.

Tag based limits

This area allow the administrator to configure tags that hide information from screens.

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).

For more information about how to configure this, please see the Affinities page.

Reset Secret

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.

  • 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".

Users04.jpg