Blind Tasks are used to allocate Tasks (such as Process Controls, Risk Treatments or any other Modules Tasks') to a Position(s) that does not have either View or Edit Security Rights to the Parent Record (e.g. the Compliance Process, Risk, or Event).
The details of a Blind Task’s Parent Record are hidden from the Position to whom the Task is allocated. (Note: if the Position has View or Edit access to this record, that higher access will apply over the Blind restrictions to the record.)
After you select the ‘Blind Task’ option, when creating or editing a Task, all Positions—including those who have no Record Security access to the Parent Record, will become visible in the ‘Actioned By’ drop-down list. Hence, now all Positions in your GRC system can be an Actioned By in the Task.
The screenshot below shows the Compliance Number is hidden for the Process Control Task.
When a Process Control hasn’t been set as a Blind Task the details of the parent Compliance shows:
The Compliance Number is displayed in the ‘Number’ column
A description of the parent Compliance is displayed above the Task details, in the ‘Details’ column
The Process Control sequence number is displayed with the Task details, in the ‘Details’ column.
By contrast, as shown above, the Blind Task hides information about the Parent Record:
The generic term Compliance is displayed in the ‘Number’ column to indicate the type of Parent Record
The description of the Parent Record in the ‘Detail’ column is no longer displayed
The Process Control sequence number is no longer displayed.
When a Task becomes due, you receive an email containing details of the Task. The screenshot below shows a sample email of a Blind Task.
Non-Blind and Blind Task email notifications (Process Control)
Note the difference between a Blind email notification and a non-Blind Notification:
The non-Blind Task notification displays the Parent Record details in the ‘Reference’ column.
The Blind Task notification displays the module name Compliance in the ‘Reference’ column to indicate the type of Parent Record, and no title of that Compliance record.
An example of when to set a Blind Task is if you want to allocate a Task to a Position but need to prevent the Position seeing the Parent Record because the information is confidential or sensitive.
Consider a Risk called Internal Fraud. The Internal Fraud Risk has a Risk Treatment assigned to the IT Officer to restrict PC access to financial records.
By making the Risk Treatment a Blind Task, we can assign the Risk Treatment to the IT Officer with confidence that the IT Officer won’t see any details about the Internal Fraud Risk. This principle applies to:
Compliance Records and their Process Controls
Risks and their Treatments
All other Modules and their Tasks.
You can set any Process Control, Risk Treatment or any other Module Task* as a Blind Task when:
creating a new Task, or
editing an existing Task.
To set a Task as a Blind Task, tick the ‘Blind Task’ option on the Task’s ‘Details’ tab while you’re editing the Task. The sample screenshots below show the Blind Task option a Process Control.
Blind Task option for Process Control
Note: The following is also applicable to Contracts.
Open a Compliance Process record.
The selected Compliance Process page is displayed.
On the Compliance Process page, click the ‘Process Controls’ tab.
The Process Controls tab content is displayed.
On the Process Controls tab, either:
Click a Process Control in the list to edit it, or
Click the ‘New Control’ icon to create a new Process Control.
The ‘New Task’ or ‘Edit Task’ window is displayed (‘New Task’ window is shown below).
On the ‘Description’ tab of the ‘New Task’ or ‘Edit Task’ window, click the ‘Blind Task’ option.
Edit the other fields of the Process Control as required.
Click the ‘Save’ icon to create or update the Process Control.