CuraWiki - User contributions [en-gb]

Main Page

2022-04-29T13:11:33Z

Admin:

__NOTOC__
{| style="border:none; background:none; text-align:center; white-space:nowrap; color:#000000;" width="100%;"


| style="text-align:center;" width="33%"|
[[Image:CURAmainlogo.png|240px]]
<div style="font-size:190%; border:none; margin:25; padding:.1em; color:#000000;">Welcome to CURA Wiki,</div>
<div style="top:; font-size:90%;">the guide to TASC Software Solutions; Child Protection Incident Recording</div>
<div id="articlecount" style="font-size:70%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>


| style="text-align:center; color:#000000;" width="33%;"|


| style="text-align:center;" width="33%"|
'''Special pages''' 
<div style="text-align:center; vertical-align: text-middle"; font-size: 6pt>
'''[[Special:Allpages|CURA Wiki Pages Index]]'''
 
'''[[FAQs|Frequently Asked Questions]]'''
|}


<center>
{| width="100%;" |
|style="border:1pt solid #CCCCCC; color:#0098DC; padding:5px; font-size:16pt;text-align:center;" width="22%;" |
<div style="float:left">[[Image:getting_started.png|32px]]</div> <div style="position:relative;top:8px">'''[[Getting started|Getting Started]]</div>
|width="4%;"|
|style="border:1pt solid #CCCCCC; color:#0098DC; padding:5px; font-size:16pt;text-align:center;" width="22%;" |
<div style="float:left">[[Image:usage.png|32px]]</div> <div style="position:relative;top:8px">'''[[:Category:Configuration|Configuration]]</div>
|width="4%;"|
|style="border:1pt solid #CCCCCC; color:#0098DC; padding:5px; font-size:16pt;text-align:center;" width="22%;" |
<div style="float:left">[[Image:configuration.png|32px]]</div> <div style="position:relative;top:8px">'''[[:Category:Usage|Usage]]</div>
|width="4%;"|
|style="border:1pt solid #CCCCCC; color:#0098DC; padding:5px; font-size:16pt;text-align:center;" width="22%;" |
<div style="float:left">[[Image:technical.png|32px]]</div> <div style="position:relative;top:8px">'''[[:Category:Technical|Technical]]</div>
|}
</center>


{| id="mp-upper" style="width: 100%; background:none;"
| class="MainPageBG" style="width:50%; vertical-align:top; color:#00000;" |
{| id="mp-left" style="vertical-align:top;"
| style="color:#008000;" |
! style="padding:2px; text-align:left" | <h2 id="mp-dyk-h2" style="margin:3px; font-size:120%; background-color:#042352; text-align:left; padding:0.2em 0.4em; color:#FFFFFF;">'''New Features'''</h2>
[[image:newfeatureimage1.jpg|thumb|right|The framework assessment matrix]]
[[image:newfeatureimage2.JPG|190px|right|A body map for recording the location of injuries]] 

'''TASC Software continue to update CURA listening to Schools, taking into consideration their individual needs as well as sharing good practice. If you have a problem to solve concerning pupil information / data tracking and you would like a new feature in CURA to save you time then please let us know.''' 

For all new features please refer the [[New features|New features'']] page, below are the recently added features. 
*[[Data Protection|Data Protection]] allows the Data Controller to manage the Data Protection for the Software
*[[Home page#Dashboard|Dashboard]] providing key information in a visual representation
*[[Students#Framework summary|Framework assessment]] displayed in table form to show number of incidences
*[[Data configuration#Adding a new website|Configurable external websites]] added to assist staff
*[[Recording information|Record and review information]] and concerns about pupils
*[[Recording information#Detail|Record the location of injuries]] on body maps
*[[Recording information#Meeting|Plan meetings and interventions]] is response to concerns
*[[Reports|Report]] on SEN, FSM, Pupil Premium and more
*[[Recording information#Documents|Upload documents]]; child protection policy, contact lists, etc.
[[image:Dash1.JPG|220px|left|Dashboard showing information taken from the framework assessment]] [[image:Table1.JPG|220px|centre|The Framework Assessment shown in a table form]]
|}


| class="MainPageBG" style="width:100%; background:#00099; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top;"
! style="padding:2px;" |

<h2 id="mp-itn-h2" style="margin:3px; background:#042352; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em;">Training & Help Guides (.pdf .doc)</h2> 

Training for Cura is available if and when required, onsite at your school. 
For further details, please contact TASC Support: 
[mailto:support@tascsoftware.co.uk support@tascsoftware.co.uk] 01902 824281 

[[Training guides|Click here'']] to see a list of guides giving illustrated step-by-step instructions to perform common tasks in CURA'''. 

|-

|-
! style="padding:2px;" |

<h2 id="mp-otd-h2" style="margin:3px; background:#042352; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em;">Customer Support and Technical Team</h2>


 For any technical queries, network questions, software updates, programming or Student review updates, please contact CURA TECHNICAL SERVICES. If you would like end user support - configurations, generate reports, new features, CURA SUPPORT DESK is available on 
'''01902 824281''' 

Suggestions, requests or issues? please post them to '''[http://support.tascsoftware.co.uk/secure.aspx Support]''' If you do not know your login, please contact either your Network Manager or CURA support desk

'''[http://www.tascsoftware.co.uk/wiki/CURA/files/downloadable%20helpdesk%20guide.pdf Guide how to use our Online Helpdesk ticket system] '''

File:Confirmedworking.jpg

2018-07-11T10:52:40Z

Admin: Admin uploaded a new version of File:Confirmedworking.jpg

File:Chronology.jpg

2018-07-06T15:03:48Z

Admin: Admin uploaded a new version of File:Chronology.jpg

File:Studentspage02.jpg

2018-07-06T10:10:35Z

Admin: Admin uploaded a new version of File:Studentspage02.jpg

Main Page

2018-05-25T15:05:56Z

Admin:

__NOTOC__
{| style="border:none; background:none; text-align:center; white-space:nowrap; color:#000000;" width="100%;"


| style="text-align:center;" width="33%"|
[[Image:CURAmainlogo.png|240px]]
<div style="font-size:190%; border:none; margin:25; padding:.1em; color:#000000;">Welcome to CURA Wiki,</div>
<div style="top:; font-size:90%;">the guide to TASC Software Solutions; Child Protection Incident Recording</div>
<div id="articlecount" style="font-size:70%;">[[Special:Statistics|{{NUMBEROFARTICLES}}]] articles</div>


| style="text-align:center; color:#000000;" width="33%;"|
'''Online demonstration sites''' 
'''[https://demo.tascsoftware.co.uk/Cura CURA demo site - Child Safeguarding Software]''' 
'''For data entry user - ''' Username: abella Password: abcd 
'''For DSL user - ''' Username: blacka Password: abcd 
'''[https://demo.tascsoftware.co.uk/INSIGHT/ INSIGHT demo site - Realtime Parental Access]''' 
Username: demo Password: demo123 
'''[https://demo.tascsoftware.co.uk/PARS PARS Connect demo site - Pupil Data Management]''' 
Username: blacka Password: abcd


| style="text-align:center;" width="33%"|
'''Special pages''' 
<div style="text-align:center; vertical-align: text-middle"; font-size: 6pt>
'''[[Special:Allpages|CURA Wiki Pages Index]]'''
 
'''[[FAQs|Frequently Asked Questions]]'''
|}


<center>
{| width="100%;" |
|style="border:1pt solid #CCCCCC; color:#0098DC; padding:5px; font-size:16pt;text-align:center;" width="22%;" |
<div style="float:left">[[Image:getting_started.png|32px]]</div> <div style="position:relative;top:8px">'''[[Getting started|Getting Started]]</div>
|width="4%;"|
|style="border:1pt solid #CCCCCC; color:#0098DC; padding:5px; font-size:16pt;text-align:center;" width="22%;" |
<div style="float:left">[[Image:usage.png|32px]]</div> <div style="position:relative;top:8px">'''[[:Category:Configuration|Configuration]]</div>
|width="4%;"|
|style="border:1pt solid #CCCCCC; color:#0098DC; padding:5px; font-size:16pt;text-align:center;" width="22%;" |
<div style="float:left">[[Image:configuration.png|32px]]</div> <div style="position:relative;top:8px">'''[[:Category:Usage|Usage]]</div>
|width="4%;"|
|style="border:1pt solid #CCCCCC; color:#0098DC; padding:5px; font-size:16pt;text-align:center;" width="22%;" |
<div style="float:left">[[Image:technical.png|32px]]</div> <div style="position:relative;top:8px">'''[[:Category:Technical|Technical]]</div>
|}
</center>


{| id="mp-upper" style="width: 100%; background:none;"
| class="MainPageBG" style="width:50%; vertical-align:top; color:#00000;" |
{| id="mp-left" style="vertical-align:top;"
| style="color:#008000;" |
! style="padding:2px; text-align:left" | <h2 id="mp-dyk-h2" style="margin:3px; font-size:120%; background-color:#042352; text-align:left; padding:0.2em 0.4em; color:#FFFFFF;">'''New Features'''</h2>
[[image:newfeatureimage1.jpg|thumb|right|The framework assessment matrix]]
[[image:newfeatureimage2.JPG|190px|right|A body map for recording the location of injuries]] 

'''TASC Software continue to update CURA listening to Schools, taking into consideration their individual needs as well as sharing good practice. If you have a problem to solve concerning pupil information / data tracking and you would like a new feature in CURA to save you time then please let us know.''' 

For all new features please refer the [[New features|New features'']] page, below are the recently added features. 
*[[Data Protection|Data Protection]] allows the Data Controller to manage the Data Protection for the Software
*[[Home page#Dashboard|Dashboard]] providing key information in a visual representation
*[[Students#Framework summary|Framework assessment]] displayed in table form to show number of incidences
*[[Data configuration#Adding a new website|Configurable external websites]] added to assist staff
*[[Recording information|Record and review information]] and concerns about pupils
*[[Recording information#Detail|Record the location of injuries]] on body maps
*[[Recording information#Meeting|Plan meetings and interventions]] is response to concerns
*[[Reports|Report]] on SEN, FSM, Pupil Premium and more
*[[Recording information#Documents|Upload documents]]; child protection policy, contact lists, etc.
[[image:Dash1.JPG|220px|left|Dashboard showing information taken from the framework assessment]] [[image:Table1.JPG|220px|centre|The Framework Assessment shown in a table form]]
|}


| class="MainPageBG" style="width:100%; background:#00099; vertical-align:top;"|
{| id="mp-right" style="width:100%; vertical-align:top;"
! style="padding:2px;" |

<h2 id="mp-itn-h2" style="margin:3px; background:#042352; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em;">Training & Help Guides (.pdf .doc)</h2> 

Training for Cura is available if and when required, onsite at your school. 
For further details, please contact TASC Support: 
[mailto:support@tascsoftware.co.uk support@tascsoftware.co.uk] 01902 824281 

[[Training guides|Click here'']] to see a list of guides giving illustrated step-by-step instructions to perform common tasks in CURA'''. 

|-

|-
! style="padding:2px;" |

<h2 id="mp-otd-h2" style="margin:3px; background:#042352; font-size:120%; font-weight:bold; text-align:left; color:#FFFFFF; padding:0.2em 0.4em;">Customer Support and Technical Team</h2>


 For any technical queries, network questions, software updates, programming or Student review updates, please contact CURA TECHNICAL SERVICES. If you would like end user support - configurations, generate reports, new features, CURA SUPPORT DESK is available on 
'''01902 824281''' 

Suggestions, requests or issues? please post them to '''[http://support.tascsoftware.co.uk/secure.aspx Support]''' If you do not know your login, please contact either your Network Manager or CURA support desk

'''[http://www.tascsoftware.co.uk/wiki/CURA/files/downloadable%20helpdesk%20guide.pdf Guide how to use our Online Helpdesk ticket system] '''

Users

2017-11-21T16:06:42Z

Admin: /* User permissions */

<div style="">
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 '''[[Installation & version updates#Optional MIS details|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'''. 

[[Image:users01.jpg|800px]] 

==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|Recording information]]''' page for more information about recording information in Cura. 
:This will have the most noticeable effect on the '''[[home page|home page]]''', which is used for reviewing incidents. 

{| class = "wikitable" cellpadding="5" style="border: 3px solid #ff8800; background: #424242;"
|-
|[[Image:curaperms2.jpg|500px]] 
| style="vertical-align:top;"|
<div style="color:#ffffff"> '''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|system settings]]'''.
'''Data entry'''
:This must be active for users to record Concerns, Meetings, Correspondances or Actions. See '''[[Recording information|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|Data Protection]]''' configuration page for your school.
'''Data configuration'''
:This allows the user to amend subcategories under Meetings, Correspondances or Actions for '''[[data configuration|data configuration]]'''. The user can also specify certain websites that are to be used under the Links area, visible under the '''[[resources|resources]]''' screen.
'''Data importer'''
:This gives access to the '''[[import|import]]''' page, used to import children and staff into Cura.
'''Archivist'''
:This gives the user access to '''[[archive|archive]]''' students or transfer the existing data to another school.
'''Resource manager'''
:Upload '''[[resources|resources]]''', such as contact forms and policies, for other users to download.
'''Resource consumer'''
:This allows users to download '''[[resources|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|reports]]''' to analyse the data that has been recorded in Cura.
</div>
|}

'''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|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|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|home page]]'''. If they have the Data Entry permission, then their login will default to the '''[[students|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#Pin number access for added security|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|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"'''. 

[[Image:users04.jpg|800px]] 

</div>
[[Category:Configuration]]

Users

2017-11-21T16:04:56Z

Admin: /* User permissions */

<div style="">
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 '''[[Installation & version updates#Optional MIS details|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'''. 

[[Image:users01.jpg|800px]] 

==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|Recording information]]''' page for more information about recording information in Cura. 
:This will have the most noticeable effect on the '''[[home page|home page]]''', which is used for reviewing incidents. 

{| class = "wikitable" cellpadding="5" style="border: 3px solid #ff8800; background: #424242;"
|-
|[[Image:curaperms2.jpg|500px]] 
| style="vertical-align:top;"|
<div style="color:#ffffff"> '''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|system settings]]'''.
'''Data entry'''
:This must be active for users to record Concerns, Meetings, Correspondances or Actions. See '''[[Recording information|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|data configuration]]'''. The user can also specify certain websites that are to be used under the Links area, visible under the '''[[resources|resources]]''' screen.
'''Data importer'''
:This gives access to the '''[[import|import]]''' page, used to import children and staff into Cura.
'''Archivist'''
:This gives the user access to '''[[archive|archive]]''' students or transfer the existing data to another school.
'''Resource manager'''
:Upload '''[[resources|resources]]''', such as contact forms and policies, for other users to download.
'''Resource consumer'''
:This allows users to download '''[[resources|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|reports]]''' to analyse the data that has been recorded in Cura.
</div>
|}

'''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|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|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|home page]]'''. If they have the Data Entry permission, then their login will default to the '''[[students|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#Pin number access for added security|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|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"'''. 

[[Image:users04.jpg|800px]] 

</div>
[[Category:Configuration]]

Users

2017-11-21T15:55:50Z

Admin: /* User permissions */

<div style="">
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 '''[[Installation & version updates#Optional MIS details|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'''. 

[[Image:users01.jpg|800px]] 

==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|Recording information]]''' page for more information about recording information in Cura. 
:This will have the most noticeable effect on the '''[[home page|home page]]''', which is used for reviewing incidents. 

{| class = "wikitable" cellpadding="5" style="border: 3px solid #ff8800; background: #424242;"
|-
|[[Image:curaperms2.jpg|500px]] 
| style="vertical-align:top;"|
<div style="color:#ffffff"> '''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|system settings]]'''.
'''Data entry'''
:This must be active for users to record Concerns, Meetings, Correspondances or Actions. See '''[[Recording information|recording information]]''' for more info.
'''Levels of need manager'''
:
'''Personal tag manager'''
:
'''Data controller'''
:
'''Data configuration'''
:This allows the user to amend subcategories under Meetings, Correspondances or Actions for '''[[data configuration|data configuration]]'''. The user can also specify certain websites that are to be used under the Links area, visible under the '''[[resources|resources]]''' screen.
'''Data importer'''
:This gives access to the '''[[import|import]]''' page, used to import children and staff into Cura.
'''Archivist'''
:This gives the user access to '''[[archive|archive]]''' students or transfer the existing data to another school.
'''Resource manager'''
:Upload '''[[resources|resources]]''', such as contact forms and policies, for other users to download.
'''Resource consumer'''
:This allows users to download '''[[resources|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|reports]]''' to analyse the data that has been recorded in Cura.
</div>
|}

'''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|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|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|home page]]'''. If they have the Data Entry permission, then their login will default to the '''[[students|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#Pin number access for added security|logging in]]''' page for more information about PIN numbers. 

'''Tag based limits'''
:

==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|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"'''. 

[[Image:users04.jpg|800px]] 

</div>
[[Category:Configuration]]

File:Curaperms2.jpg

2017-11-21T15:49:17Z

Admin: Admin uploaded a new version of File:Curaperms2.jpg

Affinities

2017-10-27T13:56:10Z

Admin:

The affinities page is used to link users to specific students, for example linking a form tutor to the pupils in their form group. Once a user has been linked to a pupil(s), the user will receive alerts whenever information is recorded for that pupil(s) '''as long as the user's clearance level is high enough to view the information'''. 

'''Step 1 - for Admin Account''' 
:To assign an affinity for a student within the '''Admin account''', simply click on the '''User name''' in the list and the affinity screen will appear, please follow '''Step 2''' below. 
[[Image:adminaffinity.jpg|600px]] 

'''Step 1 - for User Account''' 
:To assign an affinity for a student within the '''User account''' simply click on the '''affinities''' link on the '''Alerts tab''' (not available for Admin Account or Simplified interface) as shown below. In the image you can see as we have zero affinities assigned. 

[[Image:affinitieszero.jpg|200px]] 

'''Step 2 - Assigning an affinity''' 
:The following page will show every pupil that has been imported in Cura will be listed with various fields of information, such as:
*Name, DOB
*Gender, Reg
*Year, Attendance
*Ethnicity, Religion
*SEN, Gifted
*LAC, Ever in care
*SVC, FSM
*FSM6, PP
*EAL, Pregnant
*Disabled
 

{| border="0"
|width="600px"|[[Image:affinities.jpg]]
|The page can be filtered by any of the information fields to find specific pupils. To do this, click the filter button next to one of the column headers and choose how you would like to filter. Once you have selected your filter criteria, the relevant pupils will appear on the page.
|} 

[[Image:affinties_filter.jpg|250px|left]] 

The page can be filtered by any of the information fields to find specific pupils. To do this, click the filter button next to one of the column headers and choose how you would like to filter. Once you have selected your filter criteria, the relevant pupils will appear on the page. 

Scroll to the bottom of the page and click on the [[Image:AllOnOne.jpg|30px]] button to place all '''filtered''' students onto one page. Please see image below. 
[[Image:PageNumbers.jpg|500px]] 

Scroll back to the top of the page to link the user to a pupil(s) you then need to select the pupil(s) using the checkboxes on the left of the page. If a pupil has a tick in the checkbox, they are linked to the user. 

 

'''Please note that if you have filtered the screen, any pupils who have been filtered out will not be linked to the user when you click Save. Therefore you should remove any filters that you have applied before clicking the Save button at the top right, otherwise your affinities may not save correctly. 

Please note upon returning to the '''[[Home page#Alerts|Alerts tab]]''' '''(only visible in the User Account)''' you will see the number of students with whom you have an affinity displayed and if there are concerns already pending then a list will appear. 

[[Category:Configuration]]

Affinities

2017-10-27T13:55:26Z

Admin:

The affinities page is used to link users to specific students, for example linking a form tutor to the pupils in their form group. Once a user has been linked to a pupil(s), the user will receive alerts whenever information is recorded for that pupil(s) '''as long as the user's clearance level is high enough to view the information'''. 

'''Step 1 - for Admin Account''' 
:To assign an affinity for a student within the '''Admin account''', simply click on the '''User name''' in the list and the affinity screen will appear, please follow '''Step 2''' below. 
[[Image:adminaffinity.jpg|600px]] 

'''Step 1 - for User Account''' 
:To assign an affinity for a student within the '''User account''' simply click on the '''affinities''' link on the '''Alerts tab''' (not available for Admin Account or Simplified interface) as shown below. In the image you can see as we have zero affinities assigned. 

[[Image:affinitieszero.jpg|200px]] 

'''Step 2 - Assigning an affinity''' 
:The following page will show every pupil that has been imported in Cura will be listed with various fields of information, such as:
*Name, DOB
*Gender, Reg
*Year, Attendance
*Ethnicity, Religion
*SEN, Gifted
*LAC, Ever in care
*SVC, FSM
*FSM6, PP
*EAL, Pregnant
*Disabled
 

{| border="0"
|width="600px"|[[Image:affinities.jpg]]
|The page can be filtered by any of the information fields to find specific pupils. To do this, click the filter button next to one of the column headers and choose how you would like to filter. Once you have selected your filter criteria, the relevant pupils will appear on the page.
|} 

[[Image:affinties_filter.jpg|250px|left]] 

The page can be filtered by any of the information fields to find specific pupils. To do this, click the filter button next to one of the column headers and choose how you would like to filter. Once you have selected your filter criteria, the relevant pupils will appear on the page. 

Scroll to the bottom of the page and click on the [[Image:AllOnOne.jpg|30px]] button to place all '''filtered''' students onto one page. Please see image below. 
[[Image:PageNumbers.jpg|500px]] 

Scroll back to the top of the page to link the user to a pupil(s) you then need to select the pupil(s) using the checkboxes on the left of the page. If a pupil has a tick in the checkbox, they are linked to the user. 

 
 

'''Please note that if you have filtered the screen, any pupils who have been filtered out will not be linked to the user when you click Save. Therefore you should remove any filters that you have applied before clicking the Save button at the top right, otherwise your affinities may not save correctly. 

Please note upon returning to the '''[[Home page#Alerts|Alerts tab]]''' '''(only visible in the User Account)''' you will see the number of students with whom you have an affinity displayed and if there are concerns already pending then a list will appear. 

[[Category:Configuration]]

Affinities

2017-10-27T13:44:17Z

Admin:

The affinities page is used to link users to specific students, for example linking a form tutor to the pupils in their form group. Once a user has been linked to a pupil(s), the user will receive alerts whenever information is recorded for that pupil(s) '''as long as the user's clearance level is high enough to view the information'''. 

'''Step 1 - for Admin Account''' 
:To assign an affinity for a student within the '''Admin account''', simply click on the '''User name''' in the list and the affinity screen will appear, please follow '''Step 2''' below. 
[[Image:adminaffinity.jpg|600px]] 

'''Step 1 - for User Account''' 
:To assign an affinity for a student within the '''User account''' simply click on the '''affinities''' link on the '''Alerts tab''' (not available for Admin Account or Simplified interface) as shown below. In the image you can see as we have zero affinities assigned. 

[[Image:affinitieszero.jpg|200px]] 

'''Step 2 - Assigning an affinity''' 
:The following page will show every pupil that has been imported in Cura will be listed with various fields of information, such as:
*Name, DOB
*Gender, Reg
*Year, Attendance
*Ethnicity, Religion
*SEN, Gifted
*LAC, Ever in care
*SVC, FSM
*FSM6, PP
*EAL, Pregnant
*Disabled
 

[[Image:affinities.jpg|600px]] 

[[Image:affinties_filter.jpg|250px|left]] 

The page can be filtered by any of the information fields to find specific pupils. To do this, click the filter button next to one of the column headers and choose how you would like to filter. Once you have selected your filter criteria, the relevant pupils will appear on the page. 

Scroll to the bottom of the page and click on the [[Image:AllOnOne.jpg|30px]] button to place all '''filtered''' students onto one page. Please see image below. 
[[Image:PageNumbers.jpg|500px]] 

Scroll back to the top of the page to link the user to a pupil(s) you then need to select the pupil(s) using the checkboxes on the left of the page. If a pupil has a tick in the checkbox, they are linked to the user. 

'''Please note that if you have filtered the screen, any pupils who have been filtered out will not be linked to the user when you click Save. Therefore you should remove any filters that you have applied before clicking the Save button at the top right, otherwise your affinities may not save correctly. 

Please note upon returning to the '''[[Home page#Alerts|Alerts tab]]''' '''(only visible in the User Account)''' you will see the number of students with whom you have an affinity displayed and if there are concerns already pending then a list will appear. 

[[Category:Configuration]]

Admin: /* Audit Log */

The Cura software uses only '''one''' admin account. If you do not have an existing admin account then you will see a '''"Register"''' button in the top right of the login screen, allowing you to create a new admin account. 
Once an admin account has been created, the button will disappear. 

=Creating an admin account=

Before creating your admin account, you should '''download an authenticator'''. You will need this to log in to Cura in the future, as will all other users (unless disabled in user settings). There is free authenticators available on mobile app stores, including one created by Google. If you want to use the Google authenticator (available on both Android '''[https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=en_GB Google Play Store]''' and '''[https://itunes.apple.com/us/app/google-authenticator/id388497605 Apple Store]'''), you can find instructions for using it on a mobile device '''[https://support.google.com/accounts/answer/1066447?hl=en on this webpage]'''. Alternatively, you can download the Google authenticator to run on your PC from '''[https://winauth.com/download/ this link.]''' 

Once you have installed Cura and have access to an authenticator, you will need to begin creating user accounts. The first account you need to create is the admin account. Go to the Cura homepage with your unique URL (provided by the schools network manager), and click the "Register" link at the top right of the page. 

[[Image:registeraccount.jpg|600px]] 

You will then need to enter the details for the admin account, including a username, an email address and password. '''The email address that you use must be registered with us''', otherwise you will not be able to log in to Cura. If you are not sure whether your email address has been registered, please contact the '''[[Help|TASC Software Help Desk]]'''. Once done, you will be given a QR code - scan this with your phone/mobile device or enter the 20 character code into an authenticator. You will need this to log in to Cura and you will not be given another QR code, unless you '''[[FAQs#Editing or deleting the admin account|delete the admin account]]'''. 

[[Image:registration.jpg|600px]] 

You will notice that the Network time and Server time are both displayed. The server time is the time on the server that you are currently using and the Network time is the current time taken from the Internet. The difference between the two times must be less than 60 seconds otherwise users will experience problems when trying to log in. 

If the two times differ by more than 60 seconds then you need to change the time on your current server to reflect the Network time. If your current server's time is provided by another machine using the NTP protocol then you should update the time on that other machine. 

Once the times closely match each other and the Authenticator on your phone or mobile device is matching the code shown on screen, you can click the link to be taken to the Cura login screen, where you will be able to log in. 

=Giving yourself permissions=

Log in to Cura using your admin account and you will be taken to the '''[[Users#User permissions|Users]]''' page. From here, you can update permissions, set affinities or reset other users' secret codes. 

[[Image:adminperms2.jpg|right|400px|thumb|The permissions required by the admin user]] 

Select the admin user using the tickbox on the left of the page, then click the "Open" button at the top right. This will open the permissions window. You should select the following options: 

*Account manager
*Data importer
*Resource manager
*Resource consumer 

'''Please also note that the two factor login can be disabled allowing only a username and password to be used for the admin account on the login screen.'''

Then click the "Ok" button at the bottom of the window. This will update your permissions - now please refresh your browser screen for the changes to be displayed. 

=Audit Log=
{| border="0"
|width="600px"|[[Image:auditreport.jpg]]
| The system has a report built into the software for audit purposes and is '''only''' available via the admin account. The purpose of the audit log is to show from a specified date individuals who have:
* Logged into the system and from where via IP address
* Created any entries in the system
* Reviewed any information
* Deleted any information
* Run any reports
|} 

=Deleting the admin account=

If you need to amend the details of the admin account or delete it please follow the instructions provided on the following link: '''[[FAQs#Editing or deleting the admin account|deleting the admin account]]''' 

[[Category:Configuration]]

File:Auditreport.jpg

2017-10-26T15:21:07Z

Admin:

Admin account

2017-10-26T15:20:19Z

Admin:

The Cura software uses only '''one''' admin account. If you do not have an existing admin account then you will see a '''"Register"''' button in the top right of the login screen, allowing you to create a new admin account. 
Once an admin account has been created, the button will disappear. 

=Creating an admin account=

Before creating your admin account, you should '''download an authenticator'''. You will need this to log in to Cura in the future, as will all other users (unless disabled in user settings). There is free authenticators available on mobile app stores, including one created by Google. If you want to use the Google authenticator (available on both Android '''[https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=en_GB Google Play Store]''' and '''[https://itunes.apple.com/us/app/google-authenticator/id388497605 Apple Store]'''), you can find instructions for using it on a mobile device '''[https://support.google.com/accounts/answer/1066447?hl=en on this webpage]'''. Alternatively, you can download the Google authenticator to run on your PC from '''[https://winauth.com/download/ this link.]''' 

Once you have installed Cura and have access to an authenticator, you will need to begin creating user accounts. The first account you need to create is the admin account. Go to the Cura homepage with your unique URL (provided by the schools network manager), and click the "Register" link at the top right of the page. 

[[Image:registeraccount.jpg|600px]] 

You will then need to enter the details for the admin account, including a username, an email address and password. '''The email address that you use must be registered with us''', otherwise you will not be able to log in to Cura. If you are not sure whether your email address has been registered, please contact the '''[[Help|TASC Software Help Desk]]'''. Once done, you will be given a QR code - scan this with your phone/mobile device or enter the 20 character code into an authenticator. You will need this to log in to Cura and you will not be given another QR code, unless you '''[[FAQs#Editing or deleting the admin account|delete the admin account]]'''. 

[[Image:registration.jpg|600px]] 

You will notice that the Network time and Server time are both displayed. The server time is the time on the server that you are currently using and the Network time is the current time taken from the Internet. The difference between the two times must be less than 60 seconds otherwise users will experience problems when trying to log in. 

If the two times differ by more than 60 seconds then you need to change the time on your current server to reflect the Network time. If your current server's time is provided by another machine using the NTP protocol then you should update the time on that other machine. 

Once the times closely match each other and the Authenticator on your phone or mobile device is matching the code shown on screen, you can click the link to be taken to the Cura login screen, where you will be able to log in. 

=Giving yourself permissions=

Log in to Cura using your admin account and you will be taken to the '''[[Users#User permissions|Users]]''' page. From here, you can update permissions, set affinities or reset other users' secret codes. 

[[Image:adminperms2.jpg|right|400px|thumb|The permissions required by the admin user]] 

Select the admin user using the tickbox on the left of the page, then click the "Open" button at the top right. This will open the permissions window. You should select the following options: 

*Account manager
*Data importer
*Resource manager
*Resource consumer 

'''Please also note that the two factor login can be disabled allowing only a username and password to be used for the admin account on the login screen.'''

Then click the "Ok" button at the bottom of the window. This will update your permissions - now please refresh your browser screen for the changes to be displayed. 

=Audit Log=
The system has a report built into the software for audit purposes and is '''only''' available via the admin account. The purpose of the audit log is to show from a specified date individuals who have:
* Logged into the system and from where via IP address
* Created any entries in the system
* Reviewed any information
* Deleted any information
* Run any reports 

[[Image:auditreport.jpg|600px]] 

=Deleting the admin account=

If you need to amend the details of the admin account or delete it please follow the instructions provided on the following link: '''[[FAQs#Editing or deleting the admin account|deleting the admin account]]''' 

[[Category:Configuration]]

File:Users01.jpg

2017-10-26T14:54:47Z

Admin: Admin uploaded a new version of File:Users01.jpg

File:Adminperms2.jpg

2017-10-26T14:43:31Z

Admin: Admin uploaded a new version of File:Adminperms2.jpg

Main Page

File:Confirmedworking.jpg

File:Chronology.jpg

File:Studentspage02.jpg

Main Page

Users

Users

Users

File:Curaperms2.jpg

Archive

Affinities

Affinities

Affinities

File:PageNumbers.jpg

Affinities

Affinities

Affinities

File:AllOnOne.jpg

Affinities

Affinities

Admin account

Admin account

Admin account

Admin account

File:Auditreport.jpg

Admin account

File:Users01.jpg

File:Adminperms2.jpg

File:Registration.jpg

Admin account

Admin account

Admin account

Students

Students

Students

Students

Students

Students

Students

Students

Students

Students

Students

Students

Students

Students

Students

Students

Students

Students