Blind Tasks are used to allocate Process Controls, Risk Treatments or Event Tasks to Positions that do not have 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.
The ‘Blind Task’ option and Task assignment drop-down lists
If 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—become visible in the ‘Actioned By’ drop-down list and can be assigned to complete the Task.
Blind Tasks and the ‘My Summary’ page
The screenshot below shows two Process Control Tasks.
Example Risk Treatment Task entries
The first Process Control 1 hasn’t been set as a Blind Task and shows the details of the parent Compliance:
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, the Blind Task entry 2 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.
Blind Tasks and email notifications
When a Task becomes due, you receive an email containing details of the Task. The screenshot below shows two sample emails, one notifying of a non-Blind Task 1, and the other a Blind Task 2.
Non-Blind and Blind Task email notifications (Process Control)
Note the difference between the two emails (highlighted in the example above):
The non-Blind Task 1 displays the Parent Record details in the ‘Reference’ column.
The Blind Task 2 just displays the generic term Compliance in the ‘Reference’ column to indicate the type of Parent Record.
When to set a Task as a Blind Task
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
Events and their Tasks
Registers and their Tasks
Contracts and their Tasks.
How to set a Task as a Blind Task
You can set any Process Control, Risk Treatment or Event 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 for:
Process Control 1 (also applicable to Contracts),
Risk Treatment 2, and
Event Task 3 (also applicable to Registers).
Blind Task option for Process ControlBlind Task option for Risk TreatmentBlind Task option for Event Task
Procedures
Set a Process Control as a Blind Task
Note: The following is also applicable to Contracts.
Open a Compliance Process from the ‘My Tasks’ page or the ‘Compliance Processes’ page.
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
