1. Implementation Guide
  2. Designing a Security System
  3. Security for Blinded Data
  4. Interaction of Blinding Statuses and User Privileges on Executing Jobs and Viewing Data
  5. Unblinded Table Instances

Unblinded Table Instances

If all of the applicable Table instances whose Blinding flag is set to Yes have a Blinding Status of Unblinded, and the user has the Read Unblind operation on all the unblinded Table instances or the Blind Break operation on all the unblinded Table instances (and the LSH Data Blind Break User application role), the user can choose to run a job on—or view—real or dummy data.

  • Any output produced on real data has a Blinding Status of Unblinded and the Read Unblind operation on the output is required to view the output.
  • Any output produced on dummy data has a Blinding Status of Dummy and the View operation on the output is required to view the output.

If any of the applicable Table instances whose Blinding flag is set to Yes has a Blinding Status of Unlinded, and the user has only the Read Data operation on any of these blinded Table instances, the user can run a job on—or view in an IDE—only dummy data. Any outputs produced have a Blinding Status of Dummy. The View operation on outputs is required to view them.

Parent topic: Interaction of Blinding Statuses and User Privileges on Executing Jobs and Viewing Data